CVE-2026-64649

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 43% 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

Next.js is a React framework for building full-stack web applications. In versions 14.1.1 through 15.5.20 and 16.0.0 through 16.2.10, when a Server Action forwards or redirects a request, an attacker can cause the server to send that outbound request to a malicious host (Server-Side Request Forgery). This requires the attacker's request to control Host-associated headers. In some configurations, it's also possible to obtain internal values that weaken middleware/proxy authorization. Applications that use Server Actions are affected when the incoming host header is not fixed to a trusted value. This typically occurs on custom servers, or on deployments not behind a proxy that pins the host. Managed hosting pins the host upstream and is not affected; next start and standalone output do the same from version 14.2 onward. This issue has been fixed in versions 15.5.21 and 16.2.11.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
30(Track)
EG Risk 30/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
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
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_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 e3e5666ccead (vercel/next.js)

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

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

commit b51206321854 (vercel/next.js)

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

https://github.com/vercel/next.js/commit/b51206321854193208c0805ba42acc49287f942b
github Patch Available

Server-Side Request Forgery in Server Actions on custom servers · Advisory · vercel/next.js · GitHub

https://github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x

Vendor Advisories for CVE-2026-64649(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 14× in last 7d / 67× 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 126 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64649?
CVE-2026-64649 is a medium vulnerability published on July 22, 2026. Next.js is a React framework for building full-stack web applications. In versions 14.1.1 through 15.5.20 and 16.0.0 through 16.2.10, when a Server Action forwards or redirects a request, an attacker can cause the server to send that outbound request to a malicious host (Server-Side Request…
When was CVE-2026-64649 disclosed?
CVE-2026-64649 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-64649 actively exploited?
CVE-2026-64649 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 42.7% of all scored CVEs.
What is the CVSS score of CVE-2026-64649?
CVE-2026-64649 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-64649?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64649, 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-64649

Explore →

Is Your Infrastructure Affected by CVE-2026-64649?

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

Start Free Scan →Browse All CVEs