Skip to main content
Public proof of conceptFix available

CVE-2024-46982

A public proof of concept exists; no exploitation attested.

  • Published2024-09-17
  • Fixed in14.2.10 · 13.5.7
  • WeaknessCWE-639

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2024-09-1722:15CVE publishedNVD

Versions per branch

NVD · CISA-ADP · OSV
Next.js
BranchAffectedFixed in
14.x≥ 14.0.0, < 14.2.1014.2.10
13.5≥ 13.5.1, < 13.5.713.5.7

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • vercel next.js
    Affected
    • = >= 13.5.1, < 13.5.7no fix stated
    • = >= 14.0.0, < 14.2.10no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-09-17

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • @rootio/nextRoot:npmall versions · fixed in 14.2.5-root.io.5
  • @rootio/nextRoot:npmall versions · fixed in 13.5.4-root.io.2
  • @rootio/nextRoot:npmall versions · fixed in 13.5.4-root.io.3
  • @rootio/nextRoot:npmall versions · fixed in 13.5.4-root.io.4
  • @rootio/nextRoot:npmall versions · fixed in 13.5.4-root.io.5
  • @rootio/nextRoot:npmall versions · fixed in 13.5.4-root.io.6
  • @rootio/nextRoot:npmall versions · fixed in 13.5.6-root.io.2
  • @rootio/nextRoot:npmall versions · fixed in 13.5.6-root.io.3

143 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Next.js to 14.2.10 · 13.5.7

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2024-09-18
  • CNACVSS 3.17.5known since 2026-10-23
  • CNAweakness (CWE)CWE-639known since 2026-10-23
  • FIRST EPSSEPSS score61.0 %read 2026-11-20
  • PoC-in-GitHubproof of concept5known since 2026-11-01
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHigh2024-09-17

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2024-09-17
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-gp8f-8m3g-qvj9

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.

Is CVE-2024-46982 actively exploited?

Active exploitation of CVE-2024-46982 has not been confirmed. Its EPSS score was 61.0% on 2026-11-19, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-46982?

CVE-2024-46982 has a CVSS v3 base score of 7.5 (High severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running Next.js? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record