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.
CVE-2026-64654
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (54th 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 24EG Risk 24/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 computedSeverity53% × 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.8%
- EPSS %ILE
- 54th
- 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 (3)
Auto-updated Aug 6, 2026Terminal escape sequence injection in multiple `gh` commands · Advisory · cli/cli · GitHub
https://github.com/cli/cli/security/advisories/GHSA-3m3g-3wcr-px46GitHub CLI 2.97.0
Patch available: cli/cli v2.97.0
https://github.com/cli/cli/releases/tag/v2.97.0commit 2a1409fe88d4 (cli/cli)
Fix landed in cli/cli commit 2a1409fe88d4 — awaiting tagged release
https://github.com/cli/cli/commit/2a1409fe88d416cc85fc96fb5bc473f83ed5a054Vendor 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.
Affected Packages
(2 across 2 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gh | 2.23.0+dfsg1-1 ... 2.46.0-4 (16 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gh | 2.46.0-3, 2.46.0-4 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 60× 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 125 total refreshes for this CVE.
- 2026-10-05 08:24 UTCVendor advisory
- 2026-10-04 05:48 UTCEG score recompute
- 2026-10-04 05:48 UTCVendor advisory
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-02 09:38 UTCEG score recompute
- 2026-10-02 09:38 UTCVendor advisory
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-09-30 23:01 UTCEG score recompute
- 2026-09-30 23:01 UTCVendor advisory
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-29 05:53 UTCEG score recompute
- 2026-09-29 05:53 UTCVendor advisory
- 2026-09-28 13:51 UTCEPSS rescore
- 2026-09-27 17:28 UTCEG score recompute
- 2026-09-27 17:28 UTCVendor advisory
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-24 13:24 UTCEG score recompute
- 2026-09-24 13:24 UTCVendor advisory
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 13:51 UTCEG score recompute
- 2026-09-23 13:51 UTCVendor advisory
- 2026-09-22 12:52 UTCEG score recompute
- 2026-09-22 12:52 UTCVendor advisory
- 2026-09-21 12:47 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-21 12:47 UTCVendor advisory
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 03:11 UTCEG score recompute
- 2026-09-20 03:11 UTCVendor advisory
- 2026-09-19 03:10 UTCEG score recompute
- 2026-09-19 03:10 UTCVendor advisory
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 03:22 UTCEG score recompute
- 2026-09-18 03:22 UTCVendor advisory
- 2026-09-17 03:51 UTCEG score recompute
- 2026-09-17 03:51 UTCVendor advisory
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 02:58 UTCEG score recompute
- 2026-09-16 02:58 UTCVendor advisory
- 2026-09-15 01:08 UTCVendor advisory
- 2026-09-13 19:25 UTCEG score recompute
- 2026-09-13 19:25 UTCVendor advisory
- 2026-09-12 19:53 UTCEG score recompute
- 2026-09-12 19:53 UTCVendor advisory
- 2026-09-11 20:22 UTCEG score recompute
- 2026-09-11 20:22 UTCVendor advisory
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 20:38 UTCEG score recompute
- 2026-09-09 06:06 UTCEG score recompute
- 2026-09-09 06:06 UTCVendor advisory
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 17:53 UTCEG score recompute
- 2026-09-07 17:53 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 08:14 UTCEG score recompute
- 2026-09-06 08:14 UTCVendor advisory
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 08:42 UTCEG score recompute
- 2026-09-05 08:42 UTCVendor advisory
- 2026-09-04 09:11 UTCEG score recompute
- 2026-09-04 09:11 UTCVendor advisory
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 06:12 UTCEG score recompute
- 2026-09-03 06:12 UTCVendor advisory
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 22:09 UTCEG score recompute
- 2026-09-01 22:09 UTCVendor advisory
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 22:34 UTCEG score recompute
- 2026-08-31 22:34 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 15:37 UTCEG score recompute
- 2026-08-30 15:37 UTCVendor advisory
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 16:06 UTCEG score recompute
- 2026-08-29 16:06 UTCVendor advisory
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 12:00 UTCEG score recompute
- 2026-08-28 12:00 UTCVendor advisory
- 2026-08-27 09:44 UTCEG score recompute
- 2026-08-27 09:44 UTCVendor advisory
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 10:12 UTCEG score recompute
- 2026-08-26 10:12 UTCVendor advisory
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 09:58 UTCEG score recompute
- 2026-08-25 09:58 UTCVendor advisory
- 2026-08-24 10:27 UTCEG score recompute
- 2026-08-24 10:27 UTCVendor advisory
- 2026-08-23 10:55 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 11:24 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 11:52 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 12:20 UTCEG score recompute
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:gh
Frequently asked(5)
What is CVE-2026-64654?
When was CVE-2026-64654 disclosed?
Is CVE-2026-64654 actively exploited?
What is the CVSS score of CVE-2026-64654?
How do I remediate CVE-2026-64654?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64654
Is Your Infrastructure Affected by CVE-2026-64654?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.