CVE-2025-32421

LOWNVD 3.73.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2025-05-15. NVD baseline CVSS 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-14946 (ENISA EUVD) · GHSA-qpjv-v59x-3qc4 (GitHub Security Advisories)Source: ENISA EUVD

3.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 3.7Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Next.js is a React framework for building full-stack web applications. Versions prior to 14.2.24 and 15.1.6 have a race-condition vulnerability. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve pageProps data instead of standard HTML. This issue was patched in versions 15.1.6 and 14.2.24 by stripping the x-now-route-matches header from incoming requests. Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on 200 OK status without explicit cache-control headers. Those who self-host Next.js deployments and are unable to upgrade immediately can mitigate this vulnerability by stripping the x-now-route-matches header from all incoming requests at the content development network and setting cache-control: no-store for all responses under risk. The maintainers of Next.js strongly recommend only caching responses with explicit cache-control headers.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
33
EG Risk 33/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)
Severity37% × 45%
Impact severity (EG Severity): CVSS 3.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.8%
EPSS %ILE
56th
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 (3.7): severity, escalated by confirmed exploitation. This CVE's 3.7 is its impact severity (EG Severity), not escalated.

EG Severity
3.7 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

May 14, 2025

Last Modified

September 10, 2025

References (2)

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmnext @ 15.1.6 (fixes >= 15.0.0, < 15.1.6)—ghsa
npmnext @ 14.2.24 (fixes >= 0.9.9, < 14.2.24)—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)
PackageVulnerable rangeFix by version rangeDependents
next—
  • 0.9.9 up to 14.2.24: fixed in 14.2.24
  • 15.0.0 up to 15.1.6: fixed in 15.1.6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 96 of 189 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  2. 2026-11-01 08:07 UTCGHSA enrichmentGHSA-qpjv-v59x-3qc4 · GitHub severity LOW · GitHub CVSS 3.7
  3. 2026-11-01 08:07 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  7. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  8. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  9. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-10-25 16:34 UTCEG score recompute
  11. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  12. 2026-10-25 10:42 UTCEG score recompute
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  15. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  16. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  19. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  20. 2026-10-18 05:38 UTCEG score recompute
  21. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  22. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  23. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  24. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  25. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
Show 71 more
  1. 2026-10-12 17:10 UTCEG score recompute
  2. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  3. 2026-10-11 20:43 UTCEG score recompute
  4. 2026-10-11 18:53 UTCEG score recompute
  5. 2026-10-11 15:31 UTCEG score recompute
  6. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  7. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  14. 2026-10-02 14:10 UTCOSV refresh
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  16. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  17. 2026-09-29 15:19 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  18. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  19. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  20. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  21. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  22. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  23. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  24. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  25. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  26. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  27. 2026-09-13 12:13 UTCOSV refresh
  28. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  29. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  30. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  31. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  32. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  33. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  34. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  35. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  36. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  37. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  38. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  39. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  40. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  41. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  42. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  43. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  44. 2026-08-25 13:30 UTCOSV refresh
  45. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  46. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  47. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  48. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  49. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  50. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  51. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  52. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  53. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  56. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  57. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  58. 2026-08-09 05:27 UTCOSV refresh
  59. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  60. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  61. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  63. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  64. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  65. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  66. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  67. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  68. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  69. 2026-07-27 14:12 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  70. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.7% · 48th percentile
  71. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.7% · 48th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCDelfaster/CVE-2025-32421---Race-Condition-Vulnerability---Next.js
    Published Nov 26, 2025

    PoC Lab for CVE-2025-32421 – Next.js Race Condition Cache Poisoning Simulation

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-32421?
CVE-2025-32421 is a low-severity vulnerability; its CVE record was published on May 14, 2025. Next.js is a React framework for building full-stack web applications. Versions prior to 14.2.24 and 15.1.6 have a race-condition vulnerability. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve pageProps data instead of standard HTML. This…
When was the CVE record for CVE-2025-32421 published?
The CVE record for CVE-2025-32421 was published on May 14, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 10, 2025; the record at its source may have been updated since.
Is CVE-2025-32421 actively exploited?
CVE-2025-32421 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-32421?
CVE-2025-32421 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2025-32421?
A fix for CVE-2025-32421 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-32421

Explore →

Is Your Infrastructure Affected by CVE-2025-32421?

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

Book a Demo →Browse All CVEs