We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2025-49005

Next.js cache poisoning due to omission of Vary header



Description

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 vulnerability was found. The issue allowed page requests for HTML content to return a React Server Component (RSC) payload instead under certain conditions. When deployed to Vercel, this would only impact the browser cache, and would not lead to the CDN being poisoned. When self-hosted and deployed externally, this could lead to cache poisoning if the CDN does not properly distinguish between RSC / HTML in the cache keys. This issue has been resolved in Next.js 15.3.3.

Reserved 2025-05-29 | Published 2025-07-03 | Updated 2025-07-03 | Assigner GitHub_M


LOW: 3.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Problem types

CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Product status

>= 15.3.0, < 15.3.3
affected

References

github.com/...ext.js/security/advisories/GHSA-r2fc-ccr8-96c4

github.com/vercel/next.js/issues/79346

github.com/...ommit/ec202eccf05820b60c6126d6411fe16766ecc066

github.com/vercel/next.js/releases/tag/v15.3.3

vercel.com/changelog/cve-2025-49005

cve.org (CVE-2025-49005)

nvd.nist.gov (CVE-2025-49005)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2025-49005

Support options

Helpdesk Chat, Email, Knowledgebase