Next.JS vulnerability can lead to DoS via cache poisoning

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.011, the 66th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 3 Jul 2025. New records show when each source confirmed them.

Sources

• GitHub Advisory Database: GHSA-67rr-84xm-4c7r
• OSV: GHSA-67rr-84xm-4c7r
• github.com/vercel/next.js/security/advisories/GHSA-67rr-84xm-4c7r
• nvd.nist.gov/vuln/detail/CVE-2025-49826
• github.com/vercel/next.js/commit/16bfce64ef2157f2c1dfedcfdb7771bc63103fd2
• github.com/vercel/next.js/commit/a15b974ed707d63ad4da5b74c1441f5b7b120e93
• github.com/vercel/next.js
• github.com/vercel/next.js/releases/tag/v15.1.8
• vercel.com/changelog/cve-2025-49826

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.