CVE-2026-64646

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 57% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: 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, requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive memory consumption if that Server Actions uses the Edge runtime. This issue has been fixed in versions 15.5.21 and 16.2.11.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity53% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
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_release, github.
github Patch Available

Unbounded Server Action payload in Edge runtime · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-4c39-4ccg-62r3
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_commit Patch Available

commit 9a4651e754f7 (vercel/next.js)

Patch available: vercel/next.js v16.2.11 (contains commit 9a4651e754f7)

https://github.com/vercel/next.js/commit/9a4651e754f70b12e397694ffc41f44c3ba8cc17
github_commit Patch Available

commit 57c31f724d74 (vercel/next.js)

Patch available: vercel/next.js v15.5.21 (contains commit 57c31f724d74)

https://github.com/vercel/next.js/commit/57c31f724d746e86a9e8b92aa8be538a922446a4

Vendor Advisories for CVE-2026-64646(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 12× in last 7d / 64× 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 109 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64646?
CVE-2026-64646 is a medium 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, requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive memory consumption if that Server Actions uses the…
When was CVE-2026-64646 disclosed?
CVE-2026-64646 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-64646 actively exploited?
CVE-2026-64646 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 56.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64646?
CVE-2026-64646 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-64646?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64646, 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-64646

Explore →

Is Your Infrastructure Affected by CVE-2026-64646?

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

Start Free Scan →Browse All CVEs