CVE-2025-49826
nextjs: Next.js denial of service
Overview
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.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness: CWE-444
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| npm | next | >=15.0.4-canary.51, <15.1.8 | 15.1.8 |
Open a package to see all its vulnerabilities.
Operating systems · 3 fixes
Red Hat 3 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 7 | firefox | affected |
| 8 | firefox +1 | affected |
| 9 | firefox +2 | affected |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2025-49826
- github.com https://github.com/vercel/next.js
- github.com https://github.com/vercel/next.js/commit/16bfce64ef2157f2c1dfedcfdb7771bc63103fd2
- github.com https://github.com/vercel/next.js/commit/a15b974ed707d63ad4da5b74c1441f5b7b120e93
- github.com https://github.com/vercel/next.js/releases/tag/v15.1.8
- github.com https://github.com/vercel/next.js/security/advisories/GHSA-67rr-84xm-4c7r
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2025-49826
- vercel.com https://vercel.com/changelog/cve-2025-49826
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2025-49826
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.