← All security briefings

Attention

Next.js 16.4.5 and 15.5.29 close five moderate advisories covering cookies, images, response handling and cache privacy

Identifiers: CVE-2026-119346 · GHSA-f3mh-rxg3-f5g2 · CVE-2026-119347 · GHSA-7qx7-33qx-rqx2 · CVE-2026-119348 · GHSA-pc58-hwjq-p385 · CVE-2026-119349 · GHSA-rhh4-g77r-r9qj · CVE-2026-119350 · GHSA-vvgp-ww4w-46vf

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

On 19 November 2026 Vercel published five security advisories for Next.js, each rated moderate by the vendor, with fixes in 16.4.5 and backports in 15.5.29 where a 15.x line is affected. This is a separate November 19 event and is independent of the earlier React Server Components issues. The advisories group into four areas: Edge runtime cookie handling, the self-hosted image optimizer, unchanged upstream responses behind an HTTP/1.1 reverse proxy, and cache privacy in the App Router. Several paths touch confidentiality, which is why a single conditional update deserves attention even at a moderate rating. Information checked on 20 November 2026.

Classification reason: Attention: one conditional update closes several distinct confidentiality paths, including cookie exposure, cross-user cache sharing and cross-client response disclosure. The vendor rates all five advisories moderate, and the opened notices establish no public evidence of attacks in the wild as of 20 November 2026, so this briefing lists the event at attention level. This record is independent of earlier Next.js security entries.

Impact

CVE-2026-119346 (GHSA-f3mh-rxg3-f5g2) affects 15.0.0 through 15.5.28 and 16.0.0 through 16.4.4: a NextResponse that sets cookies from an Edge runtime route can expose sensitive HttpOnly cookie values to same-origin JavaScript, not to arbitrary external scripts. CVE-2026-119347 (GHSA-7qx7-33qx-rqx2) covers the same ranges: the self-hosted image optimizer can accept attacker-controlled SVG even though SVG handling is disabled by default, giving broader parser exposure and a possible denial of service, with no claim of code execution or verified data theft. CVE-2026-119348 (GHSA-pc58-hwjq-p385) affects versions up to 15.5.28 and 16.0.0 through 16.4.4: a self-hosted app that returns a fetched upstream response unchanged, behind an HTTP/1.1 reverse proxy path that permits pipelining, carries a cross-client response injection or disclosure risk. CVE-2026-119349 (GHSA-rhh4-g77r-r9qj) affects 16.0.0 through 16.4.4 only: App Router functions using the use cache directive with binary arguments may share results across distinct users. CVE-2026-119350 (GHSA-vvgp-ww4w-46vf) affects 16.4.0 through 16.4.4 only: a self-hosted next start deployment with Cache Components enabled and Partial Prefetching off can have a shared cached fallback shell poisoned through an affected fallback path, with scope and impact depending on application behavior.

Who is affected

Fixed versions are 16.4.5 for all five advisories and 15.5.29 for the three that reach the 15.x line (CVE-2026-119346, CVE-2026-119347 and CVE-2026-119348). The two cache advisories, CVE-2026-119349 and CVE-2026-119350, apply only to 16.x, and CVE-2026-119350 only from 16.4.0. Three of the five conditions expressly concern self-hosted deployments: the image optimizer under CVE-2026-119347, the reverse proxy path under CVE-2026-119348, and next start with Cache Components under CVE-2026-119350. The other two depend on feature use rather than hosting model: CVE-2026-119346 applies where an Edge runtime route sets cookies through NextResponse, and CVE-2026-119349 where App Router functions use the use cache directive with binary arguments. Managed and self-hosted deployments should be checked separately against the vendor conditions; this briefing does not claim that any managed platform is or is not affected beyond those conditions. Exposure is determined by the version actually running in each build and whether the relevant feature path is in use. The resolved version in the lockfile is one check, not the deciding fact.

Products and versions

Products and versionsAffectedFixed
Next.js Edge runtime cookie handling (CVE-2026-119346) >= 15.0.0, <= 15.5.28; >= 16.0.0, <= 16.4.4 15.5.29; 16.4.5
Next.js Self-hosted image optimization (CVE-2026-119347) >= 15.0.0, <= 15.5.28; >= 16.0.0, <= 16.4.4 15.5.29; 16.4.5
Next.js Self-hosted upstream response forwarding (CVE-2026-119348) >= 16.0.0, <= 16.4.4; <= 15.5.28 16.4.5; 15.5.29
Next.js App Router cache keys with binary arguments (CVE-2026-119349) >= 16.0.0, <= 16.4.4 16.4.5
Next.js Cache Components shared fallback (CVE-2026-119350) >= 16.4.0, <= 16.4.4 16.4.5

Exploitation evidence

Exploitation not established. As of 20 November 2026 the five opened Vercel notices describe conditions and fixes but establish no public evidence of attacks in the wild. Each issue requires a specific configuration or runtime path, such as an Edge runtime route setting cookies, a self-hosted image optimizer, a pipelining-capable HTTP/1.1 reverse proxy, binary arguments to cached functions, or Cache Components without Partial Prefetching. Confirmation of exposure should come from version and configuration checks and from authorized staging validation with test accounts, not from attack attempts.

Sources: Vercel, Vercel, Vercel, Vercel, Vercel

Actions

  1. Check the resolved version of the next dependency in each project lockfile as one input, then confirm the version actually present in the running build and compare both with the tracked ranges above.
  2. Update next to 16.4.5, or to 15.5.29 where the 15.x line is still in use, then rebuild and replace affected deployments.
  3. Confirm the active release after deployment reflects the new version, including any long-running self-hosted next start processes.
  4. Review self-hosted setups separately: image optimizer configuration, HTTP/1.1 reverse proxy pipelining behaviour, and whether Cache Components run without Partial Prefetching.
  5. For all deployments, check whether any Edge runtime route sets cookies through NextResponse and whether any App Router function uses the use cache directive with binary arguments.
  6. Validate through the normal authorized staging or QA process with test accounts and non-private test data: confirm ordinary application behaviour, and confirm that authenticated flows and cached responses stay isolated between distinct test accounts. Do not generate malicious input or attempt to reproduce the issues.

Unknowns

  • The opened vendor notices establish no public evidence of exploitation in the wild as of 20 November 2026.
  • Whether any managed hosting platform is affected depends on the vendor conditions and the platform's own runtime configuration.
  • The practical reach of cached fallback shell poisoning under CVE-2026-119350 depends on application behaviour and cannot be generalised.
  • Whether accepted SVG under CVE-2026-119347 leads beyond parser exposure or denial of service has not been established.

Sources

  • Vercel · published · retrieved https://github.com/vercel/next.js/security/advisories/GHSA-f3mh-rxg3-f5g2
  • Vercel · published · retrieved https://github.com/vercel/next.js/security/advisories/GHSA-7qx7-33qx-rqx2
  • Vercel · published · retrieved https://github.com/vercel/next.js/security/advisories/GHSA-pc58-hwjq-p385
  • Vercel · published · retrieved https://github.com/vercel/next.js/security/advisories/GHSA-rhh4-g77r-r9qj
  • Vercel · published · retrieved https://github.com/vercel/next.js/security/advisories/GHSA-vvgp-ww4w-46vf
  • Vercel · retrieved https://github.com/vercel/next.js/releases/tag/v15.5.29
  • Vercel · retrieved https://github.com/vercel/next.js/releases/tag/v16.4.5

Change history

  1. — Published: On 20 November 2026 this briefing recorded Vercel's 19 November release of Next.js 16.4.5 and 15.5.29, which closes five moderate advisories spanning Edge runtime cookie exposure, self-hosted image optimizer SVG acceptance, cross-client response handling behind HTTP/1.1 proxies, and two App Router cache privacy issues, with no public evidence of attacks in the wild.

Subscribe: RSS feed · JSON Feed · Feed format and fields