Next.js: Cache poisoning via collisions in React Server Component cache-busting
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Partial Red Hat: 8 without a fix
Attack profile from CVSS 3.1 · CNA. Fix status from CNA, GitHub and Red Hat.
Summary
Next.js is a React framework for building full-stack web applications. From 13.4.6 to before 15.5.16 and 16.2.5, React Server Component responses can be vulnerable to cache poisoning in deployments that rely on shared caches with insufficient response partitioning. In affected conditions, collisions in the _rsc cache-busting value can allow an attacker to poison cache entries so users receive the wrong response variant for a given URL. This vulnerability is fixed in 15.5.16 and 16.2.5.
Why it matters now
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 | 13.4.6 to before 15.5.16; 16.0.0 to before 16.2.5 | 15.5.16, 16.2.5 | Patch available | CNA |
| — | next (npm) | 13.4.6 to before 15.5.16 | 15.5.16 | Patch available | GHSA-vfv6-92ff-j949 |
| — | next (npm) | 16.0.0 to before 16.2.5 | 16.2.5 | Patch available | GHSA-vfv6-92ff-j949 |
- next.js Vendorvercel Affected 13.4.6 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 13.4.6 to before 15.5.16 Fixed in 15.5.16 Patch available GHSA-vfv6-92ff-j949
- next (npm) Vendor— Affected 16.0.0 to before 16.2.5 Fixed in 16.2.5 Patch available GHSA-vfv6-92ff-j949
Remediation
- Fix · CNA next.js (vercel) Fixed in 15.5.16, 16.2.5
- Fix · GHSA-vfv6-92ff-j949 next (npm) Fixed in 15.5.16 Advisory →
- Fix · GHSA-vfv6-92ff-j949 next (npm) Fixed in 16.2.5 Advisory →
Vendor assessments
Red Hat
Red Hat rating: Low. 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: Fix deferred |
Timeline
- 2026-10-02 Threatist record created from CVE-2026-44582
- 2026-10-03 Alias added: GHSA-vfv6-92ff-j949
References
More vercel Next.js vulnerabilities
- 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
Sources
- CVE-2026-44582 · CVE Program
- CVE-2026-44582 · NVD
- FIRST EPSS
- GHSA-vfv6-92ff-j949 · GitHub Advisory Database · CC BY 4.0
- CVE-2026-44582 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences