CVE-2026-64641

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.4%, top 30% of all CVEs by exploit prediction. 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: epss, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
70%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 29, 2026

Advisory Details (5)

Auto-updated Jul 27, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

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_pr 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 / EcosystemFixed in / 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 rangeFixed inDependents
next—16.2.11—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 83× 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.

Showing the most recent 100 of 139 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64641?
CVE-2026-64641 is a high vulnerability 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 CVE-2026-64641 disclosed?
CVE-2026-64641 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64641 actively exploited?
CVE-2026-64641 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 29.5% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64641, 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-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.

Start Free Scan →Browse All CVEs