CVE-2026-64654

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 48% 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, secondary
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GitHub CLI (gh) is GitHub's official command line tool. Prior to version 2.97.0, multiple GitHub CLI commands printed externally controlled gist, API, pull request, release, codespace, skill, or agent-task content without neutralizing terminal escape sequences. An attacker who can influence that content can embed escape sequences that are interpreted by the terminal of a user who runs an affected command, with impact ranging from cosmetic manipulation of the title or on-screen content to, on some terminal emulators, command execution. This extends the same class of issue as CVE-2026-45803—which addressed only gh run view --log—to the other affected command paths. This issue is fixed in version 2.97.0.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (3)

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

Terminal escape sequence injection in multiple `gh` commands · Advisory · cli/cli · GitHub

https://github.com/cli/cli/security/advisories/GHSA-3m3g-3wcr-px46
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
github_commit

commit 2a1409fe88d4 (cli/cli)

Fix landed in cli/cli commit 2a1409fe88d4 — awaiting tagged release

https://github.com/cli/cli/commit/2a1409fe88d416cc85fc96fb5bc473f83ed5a054

Vendor Advisories for CVE-2026-64654(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 27× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 12:20 UTCEG score recompute
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-19 12:49 UTCEG score recompute
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-18 13:16 UTCEG score recompute
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 13:42 UTCEG score recompute
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 14:11 UTCEG score recompute
  11. 2026-08-15 14:40 UTCEG score recompute
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 15:08 UTCEG score recompute
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 16:06 UTCEG score recompute
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-11 16:34 UTCEG score recompute
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-09 17:30 UTCEG score recompute
  20. 2026-08-09 13:47 UTCEPSS rescore
  21. 2026-08-08 17:59 UTCEG score recompute
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 18:27 UTCEG score recompute
  24. 2026-08-07 17:27 UTCEG score recompute
  25. 2026-08-06 22:22 UTCEG score recompute
Show 2 more
  1. 2026-08-06 22:16 UTCEG score recompute
  2. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64654?
CVE-2026-64654 is a medium vulnerability published on August 6, 2026. GitHub CLI (gh) is GitHub's official command line tool. Prior to version 2.97.0, multiple GitHub CLI commands printed externally controlled gist, API, pull request, release, codespace, skill, or agent-task content without neutralizing terminal escape sequences. An attacker who can influence that…
When was CVE-2026-64654 disclosed?
CVE-2026-64654 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64654 actively exploited?
CVE-2026-64654 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 48.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64654?
CVE-2026-64654 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-64654?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64654, 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

Explore the affected products and dependency analysis for CVE-2026-64654

Explore →

Is Your Infrastructure Affected by CVE-2026-64654?

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