CVE-2024-46982

HIGHNVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 59%
CISA-KEV: Not listedEPSS: 59%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(low)
EPSS
99.0%
KEV
Not listed

Published

September 17, 2024

Last Modified

September 10, 2025

References (3)

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
next—14.2.10—

Weakness Classification(1)

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 source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-22 14:07 UTCEPSS rescore
  2. 2026-07-21 15:23 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-20 17:06 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-18 10:03 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-15 16:56 UTCEPSS rescore
  11. 2026-07-15 16:56 UTCEPSS rescore
  12. 2026-07-13 22:29 UTCEPSS rescore
  13. 2026-07-13 07:08 UTCOSV refresh
  14. 2026-07-13 06:12 UTCEPSS rescore
  15. 2026-07-12 05:45 UTCEPSS rescore
  16. 2026-07-12 05:45 UTCEPSS rescore
  17. 2026-07-11 08:26 UTCEPSS rescore
  18. 2026-07-09 19:09 UTCEPSS rescore
  19. 2026-07-09 19:09 UTCEPSS rescore
  20. 2026-07-07 13:45 UTCEPSS rescore
  21. 2026-07-06 16:26 UTCEPSS rescore
  22. 2026-07-01 15:05 UTCEPSS rescore
  23. 2026-06-30 23:21 UTCEPSS rescore
  24. 2026-06-30 23:21 UTCEPSS rescore
  25. 2026-06-29 14:05 UTCEPSS rescore
Show 53 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 14:06 UTCEPSS rescore
  3. 2026-06-28 04:55 UTCEPSS rescore
  4. 2026-06-28 04:55 UTCEPSS rescore
  5. 2026-06-27 03:07 UTCEPSS rescore
  6. 2026-06-27 03:07 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-24 20:31 UTCOSV refresh
  9. 2026-06-24 14:04 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-23 21:32 UTCEPSS rescore
  12. 2026-06-23 21:32 UTCEPSS rescore
  13. 2026-06-21 14:55 UTCEPSS rescore
  14. 2026-06-21 01:58 UTCEPSS rescore
  15. 2026-06-21 01:58 UTCEPSS rescore
  16. 2026-06-17 17:52 UTCEPSS rescore
  17. 2026-06-16 17:52 UTCEPSS rescore
  18. 2026-06-16 17:52 UTCEPSS rescore
  19. 2026-06-15 17:47 UTCEPSS rescore
  20. 2026-06-14 23:17 UTCEPSS rescore
  21. 2026-06-12 23:11 UTCEPSS rescore
  22. 2026-06-12 23:11 UTCEPSS rescore
  23. 2026-06-11 13:59 UTCEPSS rescore
  24. 2026-06-10 22:18 UTCEPSS rescore
  25. 2026-06-10 13:21 UTCEPSS rescore
  26. 2026-06-08 14:16 UTCEPSS rescore
  27. 2026-06-08 14:16 UTCEPSS rescore
  28. 2026-06-07 21:16 UTCOSV refresh
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-06 13:46 UTCEPSS rescore
  31. 2026-06-05 22:46 UTCEPSS rescore
  32. 2026-06-05 22:46 UTCEPSS rescore
  33. 2026-06-05 06:09 UTCEPSS rescore
  34. 2026-06-05 06:09 UTCEPSS rescore
  35. 2026-06-04 13:11 UTCEPSS rescore
  36. 2026-06-04 13:11 UTCEPSS rescore
  37. 2026-06-02 20:12 UTCEPSS rescore
  38. 2026-06-02 20:12 UTCEPSS rescore
  39. 2026-06-01 13:51 UTCEPSS rescore
  40. 2026-06-01 13:51 UTCEPSS rescore
  41. 2026-05-31 00:16 UTCEPSS rescore
  42. 2026-05-31 00:15 UTCEPSS rescore
  43. 2026-05-29 13:43 UTCEPSS rescore
  44. 2026-05-28 13:44 UTCEPSS rescore
  45. 2026-05-28 13:44 UTCEPSS rescore
  46. 2026-05-27 13:40 UTCEPSS rescore
  47. 2026-05-27 13:40 UTCEPSS rescore
  48. 2026-05-26 13:43 UTCEPSS rescore
  49. 2026-05-26 13:43 UTCEPSS rescore
  50. 2026-05-26 07:18 UTCEPSS rescore
  51. 2026-05-26 07:18 UTCEPSS rescore
  52. 2026-05-26 07:18 UTCEPSS rescore
  53. 2026-05-23 10:42 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCLercas/CVE-2024-46982
    First seen Jan 23, 2025

    POC CVE-2024-46982

    Open source ↗

Frequently asked(5)

What is CVE-2024-46982?
CVE-2024-46982 is a high vulnerability published on September 17, 2024. 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…
When was CVE-2024-46982 disclosed?
CVE-2024-46982 was first published in the National Vulnerability Database on September 17, 2024, with the most recent update on September 10, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-46982 actively exploited?
CVE-2024-46982 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-46982?
CVE-2024-46982 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2024-46982?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-46982, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-46982

Explore →

Is Your Infrastructure Affected by CVE-2024-46982?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs