CVE-2026-64652
LOWDescription
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_<APPID>_<JWT>), 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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-201 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-60188 | High | 7.5 | 3.5% | - | - |
| CVE-2022-27779 | Medium | 5.3 | 2.7% | - | Fix |
| CVE-2017-16026 | Medium | 5.9 | 2.6% | - | Fix |
| CVE-2017-2582 | Medium | 6.5 | 2.5% | - | Fix |
| CVE-2020-26085 | Critical | 9.9 | 2.2% | - | Fix |
| CVE-2024-32825 | High | 7.5 | 2.0% | - | - |
Common questions
How do I fix CVE-2026-64652?
No published fix for CVE-2026-64652 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-64652 being actively exploited?
Not that we know of. CVE-2026-64652 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.12% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
How severe is CVE-2026-64652?
CVE-2026-64652 has a CVSS v3 base score of 3.3, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-64652
Markdown
[](https://tridentstack.com/cve/CVE-2026-64652)HTML
<a href="https://tridentstack.com/cve/CVE-2026-64652"><img src="https://tridentstack.com/cve/badge/CVE-2026-64652.svg" alt="CVE-2026-64652"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-07.