TI-2026-32484 Aliases CVE-2026-44572 GHSA-3g8h-86w9-wvmq

Next.js: Middleware / Proxy redirects can be cache-poisoned

LOW 26CWE-349Published 2026-05-13 · Updated 2026-05-14

Key facts

Attack vector: Network
Privileges required: None
User interaction: None
Attack complexity: High
Impact type: —
Confidentiality · integrity · availability: None · None · High
Fix status: Partial Red Hat: 8 without a fix

Attack profile from CVSS 3.1 · NVD. Fix status from CNA, GitHub and Red Hat.

Summary

Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, an external client could send a x-nextjs-data header on a normal request to a path handled by middleware that returns a redirect. When that happened, the middleware/proxy could treat the request as a data request and replace the standard Location redirect header with the internal x-nextjs-redirect header. Browsers do not follow x-nextjs-redirect, so the response became an unusable redirect for normal clients. If the application was deployed behind a CDN or reverse proxy that caches 3xx responses without varying on this header, a single attacker request could poison the cached redirect response for the affected path. Subsequent visitors could then receive a cached redirect response without a Location header, causing a denial of service for that redirect path until the cache entry expired or was purged. This vulnerability is fixed in 15.5.16 and 16.2.5.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV

EPSS 0.00284 21st percentileScored 2026-11-07

Fix Partial next.js (vercel): 15.5.16, 16.2.5next (npm): 15.5.16, 16.2.5Red Hat: 8 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation: None
Automatable: No
Technical impact: Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

Vendor	Product	Affected versions	Fixed in	Status	Source
vercel	next.js	12.2.0 to before 15.5.16; 16.0.0 to before 16.2.5	15.5.16, 16.2.5	Patch available	CNA
—	next (npm)	12.2.0 to before 15.5.16	15.5.16	Patch available	GHSA-3g8h-86w9-wvmq
—	next (npm)	16.0.0 to before 16.2.5	16.2.5	Patch available	GHSA-3g8h-86w9-wvmq

next.js Vendorvercel Affected 12.2.0 to before 15.5.16; 16.0.0 to before 16.2.5 Fixed in 15.5.16, 16.2.5 Patch available CNA
next (npm) Vendor— Affected 12.2.0 to before 15.5.16 Fixed in 15.5.16 Patch available GHSA-3g8h-86w9-wvmq
next (npm) Vendor— Affected 16.0.0 to before 16.2.5 Fixed in 16.2.5 Patch available GHSA-3g8h-86w9-wvmq

CPE configurations NVD · 1

CPE	Versions	Role	Vendor
cpe:2.3:a:vercel:next.js::::::node.js::*	12.2.0 to before 15.5.16; 16.0.0 to before 16.2.5	Vulnerable	vercel

cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* Versions 12.2.0 to before 15.5.16; 16.0.0 to before 16.2.5 Vulnerable ·vercel

Remediation

Fix · CNA next.js (vercel) Fixed in 15.5.16, 16.2.5
Fix · GHSA-3g8h-86w9-wvmq next (npm) Fixed in 15.5.16 Advisory →
Fix · GHSA-3g8h-86w9-wvmq next (npm) Fixed in 16.2.5 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

Product	Status	Plan or fix
Red Hat Enterprise Linux 10	Affected	No fix yet: Fix deferred
Red Hat Enterprise Linux 7	Affected	No fix yet: Fix deferred
Red Hat Enterprise Linux 8	Affected	No fix yet: Fix deferred
Red Hat Enterprise Linux 9	Affected	No fix yet: Fix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3	Affected	No fix yet: Fix deferred
Red Hat Trusted Artifact Signer	Affected	No fix yet: Fix deferred
streams for Apache Kafka 2	Affected	No fix yet: Fix deferred
streams for Apache Kafka 3	Affected	No fix yet

Timeline

2026-10-02 Threatist record created from CVE-2026-44572
2026-10-03 Alias added: GHSA-3g8h-86w9-wvmq

References

Advisory 2

Other 3

TI-2025-34861 Deserialization of untrusted data in Meta react-server-dom-webpack KEVCVSS 3.1CRITICAL 10.0
TI-2025-21309 Authorization Bypass in Next.js Middleware CVSS 3.1CRITICAL 9.1
TI-2025-34863 Deserialization of untrusted data in Meta react-server-dom-webpack CVSS 3.1HIGH 7.5
TI-2024-31371 Cache Poisoning in next.js CVSS 3.1HIGH 7.5
TI-2023-24914 Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch… CVSS 3.1HIGH 7.5
TI-2026-32490 Next.js: Server-side request forgery in applications using WebSocket upgrades CVSS 3.1HIGH 8.6

See all 62 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences