CVE-2026-44576Next.js: Cache poisoning in React Server Component responses
Updated under an hour ago ()
Does this affect you?
It affects vercel next.js. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
Next.js is a React framework for building full-stack web applications. From 14.2.0 to before 15.5.16 and 16.2.5, applications using React Server Components can be vulnerable to cache poisoning when shared caches do not correctly partition response variants. Under affected conditions, an attacker can cause an RSC response to be served from the original URL and poison shared cache entries so later visitors receive component payloads instead of the expected HTML. This vulnerability is fixed in 15.5.16 and 16.2.5.
- CVSS
- 5.4 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L
- Weakness (CWE)
- CWE-436
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- GitHub_M
- NVD analysis
- Analyzed
- Record last updated
- May 18, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
vercel next.js vercel:next.js (from the name) | from 14.2.0, < 15.5.16; from 16.0.0, < 16.2.5 | CNA record |
vercel next.js vercel:next.js | from 14.2.0 before 15.5.16; from 16.0.0 before 16.2.5 | NVD |
References
- https://github.com/vercel/next.js/security/advisories/GHSA-wfc6-r584-vfw7x-refsource-confirm, vendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.