CVE-2026-64641

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.9% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-49381 (ENISA EUVD) · GHSA-m99w-x7hq-7vfj (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Next.js is a React framework for building full-stack web applications. In versions 13.0.0 through 15.5.20 and 16.0.0 through 16.2.10, crafted requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive CPU usage blocking processing of further requests in the same process. This issue has been fixed in versions 15.5.21 and 16.2.11.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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.
Exploitation0.9% × 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
0.9%
EPSS %ILE
58th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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: 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.

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

July 22, 2026

Last Modified

October 24, 2026

Advisory Details (5)

Auto-updated Jul 27, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Denial of Service in App Router using Server Actions · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-m99w-x7hq-7vfj
GitHub release Patch Available

v16.2.11

Patch available: vercel/next.js v16.2.11

https://github.com/vercel/next.js/releases/tag/v16.2.11
GitHub release Patch Available

v15.5.21

Patch available: vercel/next.js v15.5.21

https://github.com/vercel/next.js/releases/tag/v15.5.21
GitHub pull request Patch Available

Improve performance of validating MPA form submissions

Patch available: vercel/next.js v16.3.0-canary.92 (PR #96013 merged 2026-07-21)

https://github.com/vercel/next.js/pull/96013
GitHub commit Patch Available

commit 019628571641 (vercel/next.js)

Patch available: vercel/next.js v16.3.0-canary.92 (contains commit 019628571641)

https://github.com/vercel/next.js/commit/019628571641dec57aaf349ba0c360e3964e6f12

Vendor Advisories for CVE-2026-64641(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnext2026-08-12redhat

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—
  • 13.0.0 up to 15.5.21: fixed in 15.5.21
  • 16.0.0 up to 16.2.11: fixed in 16.2.11
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 46× 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 100 of 213 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. None are among the latest 100 rows. The 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  2. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-10-27 21:05 UTCEG score recompute
  5. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  6. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-25 14:12 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-24 13:30 UTCEG score recompute
  11. 2026-10-24 13:30 UTCVendor advisory
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-10-20 11:08 UTCEG score recompute
  17. 2026-10-20 11:08 UTCVendor advisory
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  20. 2026-10-18 03:22 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  22. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
Show 75 more
  1. 2026-10-13 11:38 UTCEG score recompute
  2. 2026-10-13 11:38 UTCVendor advisory
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  4. 2026-10-12 15:47 UTCEG score recompute
  5. 2026-10-11 19:32 UTCEG score recompute
  6. 2026-10-11 16:47 UTCEG score recompute
  7. 2026-10-11 14:08 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  15. 2026-10-04 12:45 UTCEG score recompute
  16. 2026-10-04 12:45 UTCVendor advisory
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  18. 2026-10-03 03:31 UTCEG score recompute
  19. 2026-10-03 03:31 UTCVendor advisory
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  22. 2026-10-01 06:26 UTCEG score recompute
  23. 2026-10-01 06:26 UTCVendor advisory
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  25. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  26. 2026-09-28 05:14 UTCEG score recompute
  27. 2026-09-28 05:14 UTCVendor advisory
  28. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  29. 2026-09-24 10:03 UTCVendor advisory
  30. 2026-09-23 22:30 UTCEG score recompute
  31. 2026-09-23 22:30 UTCVendor advisory
  32. 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  33. 2026-09-23 10:57 UTCVendor advisory
  34. 2026-09-22 23:00 UTCEG score recompute
  35. 2026-09-22 23:00 UTCVendor advisory
  36. 2026-09-20 20:16 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  37. 2026-09-20 01:59 UTCEG score recompute
  38. 2026-09-20 01:59 UTCVendor advisory
  39. 2026-09-18 22:40 UTCEG score recompute
  40. 2026-09-18 22:40 UTCVendor advisory
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  42. 2026-09-18 03:09 UTCEG score recompute
  43. 2026-09-18 03:09 UTCVendor advisory
  44. 2026-09-17 02:05 UTCEG score recompute
  45. 2026-09-17 02:05 UTCVendor advisory
  46. 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  47. 2026-09-16 06:56 UTCEG score recompute
  48. 2026-09-16 06:56 UTCVendor advisory
  49. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  50. 2026-09-14 10:16 UTCVendor advisory
  51. 2026-09-13 22:25 UTCEG score recompute
  52. 2026-09-13 22:25 UTCVendor advisory
  53. 2026-09-13 08:26 UTCVendor advisory
  54. 2026-09-12 20:53 UTCEG score recompute
  55. 2026-09-12 20:53 UTCVendor advisory
  56. 2026-09-12 09:15 UTCVendor advisory
  57. 2026-09-11 20:28 UTCEG score recompute
  58. 2026-09-11 20:28 UTCVendor advisory
  59. 2026-09-11 14:53 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  60. 2026-09-11 09:37 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  61. 2026-09-11 08:47 UTCVendor advisory
  62. 2026-09-10 21:14 UTCEG score recompute
  63. 2026-09-10 21:14 UTCVendor advisory
  64. 2026-09-09 09:10 UTCEG score recompute
  65. 2026-09-09 09:10 UTCVendor advisory
  66. 2026-09-08 22:01 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  67. 2026-09-07 21:39 UTCEG score recompute
  68. 2026-09-07 21:39 UTCVendor advisory
  69. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  70. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.1% · 62nd percentile
  71. 2026-09-06 08:39 UTCVendor advisory
  72. 2026-09-05 19:33 UTCEG score recompute
  73. 2026-09-05 19:33 UTCVendor advisory
  74. 2026-09-05 15:31 UTCEPSS rescoreEPSS 1.1% · 61st percentile
  75. 2026-09-05 07:05 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-64641?
CVE-2026-64641 is a high-severity vulnerability; its CVE record was published on July 22, 2026. Next.js is a React framework for building full-stack web applications. In versions 13.0.0 through 15.5.20 and 16.0.0 through 16.2.10, crafted requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive CPU usage blocking processing of further…
When was the CVE record for CVE-2026-64641 published?
The CVE record for CVE-2026-64641 was published on July 22, 2026. 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 October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-64641 actively exploited?
CVE-2026-64641 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64641?
CVE-2026-64641 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-64641?
A fix for CVE-2026-64641 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64641 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64641

Explore →

Is Your Infrastructure Affected by CVE-2026-64641?

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