Next.js is a React framework for building full-stack web applications. Prior to 15.5.29 and 16.4.5, self-hosted Next.js App Router route handlers and the fetch cache that return a fetched upstream response unchanged can emit a response whose declared framing does not match the body actually sent. When the application is behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients. The resulting desynchronization can inject a response into another client's queue or disclose another client's response. This issue is fixed in versions 16.4.5 and 15.5.29.
CVE-2026-119348
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-126597 (ENISA EUVD) · GHSA-pc58-hwjq-p385 (GitHub Security Advisories)Source: ENISA EUVD
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
- CVSS
- 6.3
- EG Score
- 6.3MEDIUMmedium confidence
- EG Risk
- 44EG Risk 44/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity63% × 45%Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.5%
- EPSS %ILE
- 42nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 16, 2026
Last Modified
November 18, 2026
Advisory Details (6)
Auto-updated Nov 16, 2026November 2026 Security Release | Next.js
https://nextjs.org/blog/november-2026-security-releasev16.4.5
Patch available: vercel/next.js v16.4.5
https://github.com/vercel/next.js/releases/tag/v16.4.5v15.5.29
Patch available: vercel/next.js v15.5.29
https://github.com/vercel/next.js/releases/tag/v15.5.29commit 848ec29a3fbe (vercel/next.js)
Patch available: vercel/next.js v15.5.29 (contains commit 848ec29a3fbe)
https://github.com/vercel/next.js/commit/848ec29a3fbe68c02edb022efe19b04356997c32commit 2842833be3a5 (vercel/next.js)
Patch available: vercel/next.js v16.4.5 (contains commit 2842833be3a5)
https://github.com/vercel/next.js/commit/2842833be3a5a1e5fef0c5fb8c96df74742eef2aCross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses · Advisory · vercel/next.js · GitHub
https://github.com/vercel/next.js/security/advisories/GHSA-pc58-hwjq-p385Vendor Advisories for CVE-2026-119348(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | next @ 16.4.5 (fixes >= 16.0.0, <= 16.4.4) | — | ghsa |
| npm | next @ 15.5.29 (fixes <= 15.5.28) | — | ghsa |
These rows come from GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:45 UTCEchelonGraph re-scored
- 2026-11-21 16:45 UTCGHSA enrichmentGHSA-pc58-hwjq-p385 · GitHub severity MODERATE
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-11-21 16:28 UTCEchelonGraph re-scored
- 2026-11-21 16:28 UTCGHSA enrichmentGHSA-pc58-hwjq-p385 · GitHub severity MODERATE
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-11-20 05:17 UTCEchelonGraph re-scored
- 2026-11-20 05:17 UTCGHSA enrichmentGHSA-pc58-hwjq-p385 · GitHub severity MODERATE
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-11-18 16:28 UTCEchelonGraph re-scored
- 2026-11-18 15:28 UTCEchelonGraph re-scored
- 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-11-16 20:03 UTCENISA EUVD ID recordedEUVD-2026-126597 · Source: ENISA EUVD
- 2026-11-16 19:38 UTCEchelonGraph re-scored
- 2026-11-16 18:50 UTCEchelonGraph re-scoredFirst assessed: 6.3 MEDIUM
- 2026-11-16 18:48 UTCMITRE cvelistV5first tracked
Publicly available exploits
(1 reference)Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.
- GitHub PoCaheybati/CVE-2026-119348Published Nov 20, 2026
public PoC for CVE-2026-119348 cross-client response injection/disclosure in self-hosted Next.js. Dual-lab + differential exploit.
Open source ↗
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-119348?
When was the CVE record for CVE-2026-119348 published?
Is CVE-2026-119348 actively exploited?
What is the CVSS score of CVE-2026-119348?
How do I remediate CVE-2026-119348?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-119348
Is Your Infrastructure Affected by CVE-2026-119348?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.