CVE-2024-46982

CVE-2024-46982 is a high-severity vulnerability in Vercel Next.js with a CVSS 3.x base score of 7.5. Its EPSS exploit-prediction score of 59% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-639.

Key facts

Description

Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a `Cache-Control: s-maxage=1, stale-while-revalidate` header which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1. Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered routes e.g. `pages/dashboard.tsx` not `pages/blog/[slug].tsx`. This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not. There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.

Frequently asked questions

What is CVE-2024-46982?
Next.js is a React framework for building full-stack web applications. By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a `Cache-Control: s-maxage=1, stale-while-revalidate` header which some upstream CDNs may cache as well. To be potentially affected all of the following must apply: 1. Next.js between 13.5.1 and 14.2.9, 2. Using pages router, & 3. Using non-dynamic server-side rendered routes e.g. `pages/dashboard.tsx` not `pages/blog/[slug].tsx`. This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not. There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.
How severe is CVE-2024-46982?
CVE-2024-46982 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2024-46982 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 59% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-46982?
CVE-2024-46982 affects Vercel Next.js. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-46982?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-46982 have an EU (EUVD) identifier?
Yes. CVE-2024-46982 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-2803.
When was CVE-2024-46982 published?
CVE-2024-46982 was published on 2024-09-17 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Vercel Next.js

All CVEs affecting Vercel Next.js →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →