Next.js has a Cache poisoning vulnerability due to omission of the Vary header
### Summary A cache poisoning issue in **Next.js App Router >=15.3.0 and < 15.3.3** may have allowed RSC payloads to be cached and served in place of HTML, under specific conditions involving middleware and redirects. This issue has been fixed in **Next.js 15.3.3**. Users on affected versions should **upgrade immediately** and **redeploy** to ensure proper caching behavior. More details: [CVE-2025-49005](https://vercel.com/changelog/cve-2025-49005)
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-49005US | — | — | ||
Next.js is a React framework for building full-stack web applications. In Next.js App Router from 15.3.0 to before 15.3.3 and Vercel CLI from 41.4.1 to 42.2.0, a cache poisoning vu… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/vercel/next.jsPACKAGE
- https://github.com/vercel/next.js/commit/ec202eccf05820b60c6126d6411fe16766ecc066WEB
- https://github.com/vercel/next.js/issues/79346WEB
- https://github.com/vercel/next.js/pull/79939WEB
- https://github.com/vercel/next.js/releases/tag/v15.3.3WEB
- https://github.com/vercel/next.js/security/advisories/GHSA-r2fc-ccr8-96c4WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-49005ADVISORY
- https://vercel.com/changelog/cve-2025-49005WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan