CVE-2026-64649

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (39th 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-49571 (ENISA EUVD) · GHSA-89xv-2m56-2m9x (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.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 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.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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.5%
EPSS %ILE
39th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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: 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.

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

July 22, 2026

Last Modified

October 24, 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 advisoryMentions a patch (unverified)

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64649?
CVE-2026-64649 is a medium-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 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 the CVE record for CVE-2026-64649 published?
The CVE record for CVE-2026-64649 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-64649 actively exploited?
CVE-2026-64649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-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?
A fix for CVE-2026-64649 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64649 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-64649

Explore →

Is Your Infrastructure Affected by CVE-2026-64649?

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

Book a Demo →Browse All CVEs