CVE-2025-49826 Details
Description
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.
A cache poisoning vulnerability has been identified in Next.js, a React framework for full-stack web applications. This issue affects versions 15.0.4-canary.51 prior to 15.1.8. The vulnerability can lead to a denial-of-service condition by allowing a HTTP 204 response to be cached for static pages. As a result, the 204 response could be served to all users accessing the page. This issue does not impact customers hosted on Vercel.
Users can upgrade to Next.js version 15.1.8 or later to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 8, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-444 | Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| vercel next.js | > 15.0.4, < 15.1.8 15.0.4 canary51 15.0.4 canary52 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Sep 10, 2025 | Initial Analysis | [email protected] |
| Jul 3, 2025 | CVE Modified | [email protected] |
| Jul 3, 2025 | New CVE Received | [email protected] |