CVE-2025-49826
unknown
CVSS v3
—
CVSS v4 NEW
—
VIR risk
—
Description
Next.JS vulnerability can lead to DoS via cache poisoning
Predictions
Exploit likelihood
30%
Patch ETA
—
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| npm | next | >=15.0.4-canary.51,<15.1.8 | 15.1.8 |
References
- https://github.com/vercel/next.js/security/advisories/GHSA-67rr-84xm-4c7r
- https://nvd.nist.gov/vuln/detail/CVE-2025-49826
- https://github.com/vercel/next.js/commit/16bfce64ef2157f2c1dfedcfdb7771bc63103fd2
- https://github.com/vercel/next.js/commit/a15b974ed707d63ad4da5b74c1441f5b7b120e93
- https://github.com/vercel/next.js
- https://github.com/vercel/next.js/releases/tag/v15.1.8
- https://vercel.com/changelog/cve-2025-49826
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.