vercel/next.js · Security
Next.js has a Cache poisoning vulnerability due to omission of the Vary header
- GHSA ID
- GHSA-r2fc-ccr8-96c4
- CVE ID
- CVE-2025-49005
- Severity
- low
- Published
- Updated
- CVSS
- 3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
- CVSS v3
- 3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Description
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
CWEs
- CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
References
- https://github.com/vercel/next.js/security/advisories/GHSA-r2fc-ccr8-96c4 ↗
- https://github.com/vercel/next.js/pull/79939 ↗
- https://github.com/vercel/next.js/releases/tag/v15.3.3 ↗
- https://vercel.com/changelog/cve-2025-49005 ↗
- https://nvd.nist.gov/vuln/detail/CVE-2025-49005 ↗
- https://github.com/vercel/next.js/issues/79346 ↗
- https://github.com/vercel/next.js/commit/ec202eccf05820b60c6126d6411fe16766ecc066 ↗
- https://github.com/advisories/GHSA-r2fc-ccr8-96c4 ↗