CVE-2026-64652

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th 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
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GitHub CLI (gh) is GitHub's official command line tool. Prior to version 2.97.0, gh auth status masked only the characters after the last underscore in certain fine-grained personal access tokens and GitHub App tokens. As a result, part of an affected token could appear in terminal or CI output that is captured or shared. Authenticated users are affected if they ran gh auth status (without the --show-token flag) with a token type whose format contains an underscore after the prefix. This includes fine-grained personal access tokens (github_pat_*) and GitHub App installation and user access tokens (ghs_*, ghu_*; for example, ghs__), as well as the Actions GITHUB_TOKEN. Classic tokens such as gho_* and ghp_* have an underscore-free body and are not affected. This issue is fixed in version 2.97.0.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/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
Severity33% × 45%
Exploitation0% × 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.2%
EPSS %ILE
4th
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

References (3)

Vendor Advisories for CVE-2026-64652(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 9× in last 7d / 36× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 05:49 UTCEG score recompute
  3. 2026-10-04 05:49 UTCVendor advisory
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 23:05 UTCEG score recompute
  8. 2026-09-30 23:05 UTCVendor advisory
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 17:28 UTCEG score recompute
  12. 2026-09-27 17:28 UTCVendor advisory
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-22 21:20 UTCEG score recompute
  16. 2026-09-22 21:20 UTCVendor advisory
  17. 2026-09-19 21:26 UTCEG score recompute
  18. 2026-09-19 21:26 UTCVendor advisory
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-17 00:57 UTCEG score recompute
  21. 2026-09-17 00:57 UTCVendor advisory
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-13 16:58 UTCEG score recompute
  25. 2026-09-13 16:58 UTCVendor advisory
Show 50 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-10 20:39 UTCEG score recompute
  4. 2026-09-09 06:06 UTCEG score recompute
  5. 2026-09-09 06:06 UTCVendor advisory
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 02:32 UTCEG score recompute
  10. 2026-09-06 02:32 UTCVendor advisory
  11. 2026-09-05 15:31 UTCEPSS rescore
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-03 06:12 UTCEG score recompute
  14. 2026-09-03 06:12 UTCVendor advisory
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 16:10 UTCEG score recompute
  20. 2026-08-30 16:10 UTCVendor advisory
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:42 UTCEPSS rescore
  23. 2026-08-27 19:50 UTCEG score recompute
  24. 2026-08-27 19:50 UTCVendor advisory
  25. 2026-08-26 14:47 UTCEPSS rescore
  26. 2026-08-25 13:49 UTCEPSS rescore
  27. 2026-08-24 20:30 UTCEG score recompute
  28. 2026-08-24 20:30 UTCVendor advisory
  29. 2026-08-22 00:06 UTCEG score recompute
  30. 2026-08-21 23:49 UTCEPSS rescore
  31. 2026-08-20 22:55 UTCEPSS rescore
  32. 2026-08-19 17:04 UTCEPSS rescore
  33. 2026-08-19 03:46 UTCEG score recompute
  34. 2026-08-18 13:48 UTCEPSS rescore
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 07:26 UTCEG score recompute
  38. 2026-08-15 01:30 UTCEPSS rescore
  39. 2026-08-13 22:00 UTCEPSS rescore
  40. 2026-08-13 11:07 UTCEG score recompute
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-10 14:47 UTCEG score recompute
  44. 2026-08-09 13:47 UTCEPSS rescore
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-07 18:27 UTCEG score recompute
  47. 2026-08-07 17:47 UTCEG score recompute
  48. 2026-08-06 22:22 UTCEG score recompute
  49. 2026-08-06 22:16 UTCEG score recompute
  50. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-64652?
CVE-2026-64652 is a low vulnerability published on August 6, 2026. GitHub CLI (gh) is GitHub's official command line tool. Prior to version 2.97.0, gh auth status masked only the characters after the last underscore in certain fine-grained personal access tokens and GitHub App tokens. As a result, part of an affected token could appear in terminal or CI output…
When was CVE-2026-64652 disclosed?
CVE-2026-64652 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-64652 actively exploited?
CVE-2026-64652 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64652?
CVE-2026-64652 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64652?
A fix for CVE-2026-64652 is available — its CVE record says: "This issue is fixed in version 2.97.0." The vendor advisories EchelonGraph has for CVE-2026-64652 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-64652

Explore →

Is Your Infrastructure Affected by CVE-2026-64652?

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

Book a Demo →Browse All CVEs