Next.js 15.0.4–15.1.7 Cache Poisoning DoS (HTTP 204) – Fixed 15.1.8
CVE-2025-49826 Published on July 3, 2025
Next.js DoS vulnerability via cache poisoning
Next.js is a React framework for building full-stack web applications. From versions 15.0.4-canary.51 to before 15.1.8, a cache poisoning bug leading to a Denial of Service (DoS) condition was found in Next.js. This issue does not impact customers hosted on Vercel. Under certain conditions, this issue may allow a HTTP 204 response to be cached for static pages, leading to the 204 response being served to all users attempting to access the page. This issue has been addressed in version 15.1.8.
Vulnerability Analysis
CVE-2025-49826 is exploitable with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity, and a high impact on availability.
Weakness Type
What is a HTTP Request Smuggling Vulnerability?
When malformed or abnormal HTTP requests are interpreted by one or more entities in the data flow between the user and the web server, such as a proxy or firewall, they can be interpreted inconsistently, allowing the attacker to "smuggle" a request to one device without the other device being aware of it.
CVE-2025-49826 has been classified to as a HTTP Request Smuggling vulnerability or weakness.
Products Associated with CVE-2025-49826
Want to know whenever a new CVE is published for Vercel Next Js? stack.watch will email you.
Affected Versions
vercel next.js Version >= 15.0.4-canary.51, < 15.1.8 is affected by CVE-2025-49826Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.