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.
CVE-2024-46982
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.3 because EPSS predicted 59% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
Also known asEUVD-2024-2803 (ENISA EUVD) · GHSA-gp8f-8m3g-qvj9 (GitHub Security Advisories)Source: ENISA EUVD
- High exploitation likelihood — EPSS 59%
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 8.3HIGHhigh confidence
- EG Risk
- 72EG Risk 72/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation59% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 59%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 59% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 17, 2024
Last Modified
September 10, 2025
Advisory Details (3)
Auto-updated Oct 27, 2026Cache Poisoning · Advisory · vercel/next.js · GitHub
https://github.com/vercel/next.js/security/advisories/GHSA-gp8f-8m3g-qvj9commit bd164d53af25 (vercel/next.js)
Fix landed in vercel/next.js commit bd164d53af25 — awaiting tagged release
https://github.com/vercel/next.js/commit/bd164d53af259c05f1ab434004bcfdd3837d7cdacommit 7ed7f125e07e (vercel/next.js)
Fix landed in vercel/next.js commit 7ed7f125e07e — awaiting tagged release
https://github.com/vercel/next.js/commit/7ed7f125e07ef0517a331009ed7e32691ba403d3Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | next @ 13.5.7 (fixes >= 13.5.1, < 13.5.7) | — | ghsa |
| npm | next @ 14.2.10 (fixes >= 14.0.0, < 14.2.10) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| next | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 37× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 93 of 172 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 79 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:31 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-11-01 08:12 UTCGHSA enrichmentGHSA-gp8f-8m3g-qvj9 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-01 08:12 UTCEG score recompute
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-29 16:31 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-28 16:29 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-27 22:01 UTCEG score recompute
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-25 17:01 UTCEG score recompute
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-24 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-21 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-20 10:46 UTCEG score recompute
- 2026-10-19 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-18 06:58 UTCEG score recompute
- 2026-10-17 16:31 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-16 16:37 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-15 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-13 16:31 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-12 17:43 UTCEG score recompute
Show 68 moreShow fewer
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-11 21:09 UTCEG score recompute
- 2026-10-11 16:01 UTCEG score recompute
- 2026-10-11 13:46 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-10 19:58 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-09 23:25 UTCOSV refresh
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-08 17:08 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-06 15:16 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-04 23:20 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-03 14:24 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-30 19:54 UTCEG score recompute
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-26 15:57 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-22 14:47 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-20 07:43 UTCOSV refresh
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-17 19:27 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-16 05:12 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-12 14:59 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-11 14:51 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-11 09:35 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-10 09:33 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-04 13:59 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-02 14:10 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-09-01 10:59 UTCOSV refresh
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-25 13:47 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-24 14:15 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-23 00:18 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-20 22:54 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-16 02:13 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-15 10:07 UTCOSV refresh
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-13 21:59 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-07 16:25 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-06 13:45 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-04 15:08 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-04 10:36 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-08-01 04:14 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-07-30 22:21 UTCOSV refresh
- 2026-07-30 16:26 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-07-30 01:29 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-07-28 15:35 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-07-26 14:53 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-07-25 14:16 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-07-24 14:16 UTCEPSS rescoreEPSS 59% · 99th percentile
- 2026-07-23 14:17 UTCEPSS rescoreEPSS 59% · 99th percentile
Publicly available exploits
(1 reference)Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.
- GitHub PoCLercas/CVE-2024-46982Published Jan 23, 2025
POC CVE-2024-46982
Open source ↗
Related CVEs(same product + same CWE)
Same product
10 shownnpm:next
Frequently asked(5)
What is CVE-2024-46982?
When was the CVE record for CVE-2024-46982 published?
Is CVE-2024-46982 actively exploited?
What is the CVSS score of CVE-2024-46982?
How do I remediate CVE-2024-46982?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-46982
Is Your Infrastructure Affected by CVE-2024-46982?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.