CVE-2026-64653

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-54213 (ENISA EUVD) · GHSA-4fjg-2h4q-fwg3 (GitHub Security Advisories) · GO-2026-6765 (OSV.dev)Source: ENISA EUVD

5.1EG
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: 5.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.97.0, some HTTP request URLs interpolate variable path components without percent encoding, allowing URL path metacharacters in attacker-controlled repository or resource values to make gh address a different API endpoint or resource than the user intended. This issue is fixed in version 2.97.0.

CVSS
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
23
EG Risk 23/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)
Severity51% × 45%
Impact severity (EG Severity): CVSS 5.1 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
44th
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 (5.1): severity, escalated by confirmed exploitation. This CVE's 5.1 is its impact severity (EG Severity), not escalated.

EG Severity
5.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

August 6, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
Patch available. Sources: github, github_release.
GitHub advisoryMentions a patch (unverified)

Unescaped variable components in request URLs could allow path traversal in GitHub CLI · Advisory · cli/cli · GitHub

https://github.com/cli/cli/security/advisories/GHSA-4fjg-2h4q-fwg3
GitHub release Patch Available

GitHub CLI 2.97.0

Patch available: cli/cli v2.97.0

https://github.com/cli/cli/releases/tag/v2.97.0

Vendor Advisories for CVE-2026-64653(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
gogithub.com/cli/cli/v2 @ 2.97.0 (fixes < 2.97.0)—ghsa

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

(4 across 3 ecosystems)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
github.com/cli/cli—
  • every version on: no fix on record
—
github.com/cli/cli/v2—
  • every version up to 2.97.0: fixed in 2.97.0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gh2.23.0+dfsg1-1 ... 2.46.0-4 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gh2.46.0-3, 2.46.0-4
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 179 rows 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 79 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-64653?
CVE-2026-64653 is a medium-severity vulnerability; its CVE record was published on August 6, 2026. GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.97.0, some HTTP request URLs interpolate variable path components without percent encoding, allowing URL path metacharacters in attacker-controlled repository or resource values to make gh address a different API endpoint or…
When was the CVE record for CVE-2026-64653 published?
The CVE record for CVE-2026-64653 was published on August 6, 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 September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-64653 actively exploited?
CVE-2026-64653 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64653?
CVE-2026-64653 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64653?
A fix for CVE-2026-64653 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64653 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-64653

Explore →

Is Your Infrastructure Affected by CVE-2026-64653?

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

Book a Demo →Browse All CVEs