Next.js: Cross-client response injection and disclosure
Affects nextSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 16.4.5 when convenient.
Data as of 19 Nov 2026, 23:07 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 16.4.5, 15.5.29
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade next to 16.4.5; next to 15.5.29.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnext | Affected
| Fixed in
|
| npmnext | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied by upgrading Next.js to versions 16.4.5 or later, or 15.5.29 or later. Applying these fixed versions fully mitigates the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
A vulnerability in self-hosted Next.js applications using App Router route handlers and fetch cache can cause cross-client response injection and disclosure. This occurs when the application returns an upstream fetched response unchanged, leading to mismatched response framing. When deployed behind an HTTP/1.1 reverse proxy that allows pipelined response queueing, crafted upstream responses can desynchronize client responses, enabling injection and disclosure of other clients' data. Fixed versions 16.4.5 and 15.5.29 address this issue.
References
- github.com/vercel/next.js/security/advisories/GHSA-pc58-hwjq-p385 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-119348 (opens in a new tab)
- github.com/vercel/next.js/commit/2842833be3a5a1e5fef0c5fb8c96df74742eef2a (opens in a new tab)
- github.com/vercel/next.js/commit/848ec29a3fbe68c02edb022efe19b04356997c32 (opens in a new tab)
- github.com/vercel/next.js (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v15.5.29 (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v16.4.5 (opens in a new tab)
- nextjs.org/blog/november-2026-security-release (opens in a new tab)