CVE-2026-64653

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). 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, secondary
Trending — 3 sources updated this week
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • 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 v3
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
23
EG Risk 23/100CISA SSVC

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
Severity51% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 6, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
Patch available. Sources: github, github_release.
github Patch Available

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(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
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 15× in last 7d / 63× 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 128 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-64653?
CVE-2026-64653 is a medium vulnerability 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 CVE-2026-64653 disclosed?
CVE-2026-64653 was first published on August 6, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (42nd 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