CVE-2026-119346 json
HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
published 6d ago modified 3d ago also GHSA-f3mh-rxg3-f5g2
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository vercel/next.js. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.
- cvss
- 6.0
- version 4.0, the maintainers
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of vercel/next.js for next: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Patch / fix
- npm next 15.5.29, 16.4.5
Is CVE-2026-119346 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| the maintainers | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | next | >=16.0.0, <=16.4.4 >=15.0.0, <=15.5.28 |
16.4.5 15.5.29 |
Classification
- Technology feeds
References
Sources
- Maintainer advisory GHSA-f3mh-rxg3-f5g2
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of vercel/next.js published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.