CVE-2026-64652: GitHub CLI: Partial token disclosure in `gh auth status` output
Noroxi assessment
Priority: Monitor (action score 13/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: cli cli 2.97.0; azl3 gh 2.62.0-20 on Azure Linux 3.0 2.97.0-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to cli cli 2.97.0; azl3 gh 2.62.0-20 on Azure Linux 3.0 2.97.0-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 6, 2026
- Updated
- Sep 10, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-201
Report tools
Action score
13
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 3.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
cli cli
- < 2.97.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | gh | from 0 | — |
| Go | github.com/cli/cli | from 0 | — |
| Go | github.com/cli/cli/v2 | before 2.97.0 | 2.97.0 |
| openSUSE:Leap 16.0 | gh | before 2.98.0-bp160.1.1 | 2.98.0-bp160.1.1 |
| openSUSE:Tumbleweed | gh | before 2.97.0-1.1 | 2.97.0-1.1 |
Same product
cli: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-53858Recursive repository cloning can leak authentication tokens to non-GitHub submodule hosts in the gh cli26Monitor
- CVE-2025-25204`gh attestation verify` returns incorrect exit code during verification if no attestations are present25Monitor
- CVE-2024-54132GitHub CLI allows downloading malicious GitHub Actions workflow artifact to result in path traversal vulnerability25Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-59831Jul 9, 2026 · GitHub CLI `gh codespace jupyter` could allow remote code execution when connecting to a malicious Codespace17Monitor
- Later →CVE-2026-64653Aug 6, 2026 · GitHub CLI: Unescaped variable components in request URLs could allow path traversal20Monitor
- Later →CVE-2026-64654Aug 6, 2026 · GitHub CLI: Terminal escape sequence injection in multiple `gh` commands21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| cli cli | 2.97.0 · description | Vendor (CNA) |
| azl3 gh 2.62.0-20 on Azure Linux 3.0 | 2.97.0-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| Go:github.com/cli/cli/v2 | 2.97.0 | Package registry (OSV) |
| opensuse:gh | 2.97.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0776 · Aug 7, 2026(GitHub CLI Güvenlik Bildirimi)
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-201 · Insertion of Sensitive Information Into Sent DataCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Choosing Message IdentifierCAPEC-12likelihood: High · High
- Exploiting Incorrectly Configured SSL/TLSCAPEC-217likelihood: Low
- WiFi MAC Address TrackingCAPEC-612Low
- WiFi SSID TrackingCAPEC-613Low
- Cellular Broadcast Message RequestCAPEC-618Low
- Signal Strength TrackingCAPEC-619Low
- Analysis of Packet Timing and SizesCAPEC-621Low
- Electromagnetic Side-Channel AttackCAPEC-622Low
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.