Skip to main content
Menu
CVEs

CVE

Next.js cross-client response injection in fetch forwarding

CVE-2026-119348EUVD-2026-126597

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 15.5.29, 16.4.5
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 15.5.29, 16.4.5.

Published
Last modified
Reference
Last checked
40/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Next.js is affected. An attacker can remotely, without logging in, send a crafted upstream response that desynchronizes responses between clients, letting them inject a response into another client's queue or read another client's response. This only occurs in self-hosted apps that forward fetched responses behind an HTTP/1.1 reverse proxy that allows pipelined response queueing.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.now Index

40Pcve.now Index 40 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach17/20Affects Next.js (a widely deployed server, runtime, framework or database)
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 85 if added to CISA KEV
  • Would score about 80 if CISA's SSVC rates exploitation active
  • Would score about 45 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 15.5.29, 16.4.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-119348 (Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119348 (entry last updated 2026-11-16):
Affected:
- vercel next.js: fixed in 15.5.29; from 16.0.0, fixed in 16.4.5
Fixed versions: 15.5.29, 16.4.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119348 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119348 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vercel/next.js/security/advisories/GHSA-pc58-hwjq-p385
- https://github.com/vercel/next.js/commit/2842833be3a5a1e5fef0c5fb8c96df74742eef2a
- https://github.com/vercel/next.js/commit/848ec29a3fbe68c02edb022efe19b04356997c32
- https://github.com/vercel/next.js/releases/tag/v15.5.29
- https://github.com/vercel/next.js/releases/tag/v16.4.5
- https://nextjs.org/blog/november-2026-security-release
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119348
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119348"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • vercel next.js

    fixed in 15.5.29; From 16.0.0 · fixed in 16.4.5

Evidence 8

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Repository
  2. Repository
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-119348

Is CVE-2026-119348 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-119348?

next.js: before 15.5.29; from 16.0.0 before 16.4.5.Source: cve.now feed data

How do I fix CVE-2026-119348?

Upgrade to a fixed version: 15.5.29, 16.4.5.Source: cve.now feed data