vercel · Next.js · published 2026-05-13
CVE-2026-44582Next.js: Cache poisoning via collisions in React Server Component cache-busting
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-44582 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 12% of all CVEs. This Next.js vulnerability: CVSS 3.7 (v3.1). Fixed upstream in Next.js 16.2.5, 15.5.16. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Next.js 16.2.5, 15.5.16.
Patch events
Web frameworkNext.js
Next.js security releases: 16.2.5, 15.5.16
Upgrade to
16.2.515.5.16Why: CVE-2026-44578: EPSS 36% with high severity (CVSS 8.6).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (12th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 3.7 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vercel next.js
>= 13.4.6, < 15.5.16(affected)>= 16.0.0, < 16.2.5(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.