github.com/cli/cli/v2
Affected
- introduced
0, fixed2.97.0(semver)
Fixed versions
2.97.0
Fix
- Fixed version
2.97.0go get github.com/cli/cli/[email protected]
Advisory
Also known as: CVE-2026-64652, GO-2026-6766
GitHub CLI partially discloses authentication tokens in gh auth status output
Summary
A security vulnerability has been identified in GitHub CLI where gh auth status could potentially print a portion of the authentication token in plaintext, depending on the lexical structure of the token.
Affected users:
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/user access tokens (ghs_*, ghu_*, e.g., ghs_<APPID>_<JWT>), including the Actions GITHUB_TOKEN. Classic tokens such as gho_* and ghp_* have an underscore-free body and are not affected.Details
The vulnerability stems from the way GitHub CLI masks the authentication token when reporting authentication state:
gh auth status without --show-token, expecting the token to be fully masked.Because gh auth status is a diagnostic command commonly run interactively and inside automated environments, the leaked token characters can end up in CI/CD job logs, terminal scrollback, screen recordings, screenshots, or pasted output shared in bug reports and support requests.
In v2.97.0, GitHub CLI fully masks the token in gh auth status output, preserving only the known token prefix and redacting the remainder unless --show-token is explicitly provided.
Impact
Running gh auth status in a context where the output is captured, logged, or shared could leak a portion of an affected token. The affected token types are fine-grained personal access tokens (github_pat_*) and GitHub App installation/user access tokens (ghs_*, ghu_*, e.g., ghs_<APPID>_<JWT>), including the Actions GITHUB_TOKEN. Installation and Actions tokens are short-lived, which narrows the window in which a recovered token could be reused. See GitHub credential types.
Remediation and Mitigation
gh to v2.97.0.gh auth status output may have been captured or shared:github_pat_*):** regenerate the token from your account settings. See Managing your personal access tokens.ghs_*, ghu_*, e.g., ghs_<APPID>_<JWT>):** these are short-lived and rotate automatically (See GitHub credential types). If you believe a token was captured while still valid, you can revoke it immediately using the Revoke an installation access token REST endpoint (DELETE /installation/token). To cut off a third-party app's access more broadly, suspend or uninstall the app from the web UI. See Reviewing and modifying installed GitHub Apps.gh auth status in contexts where the output is captured or shared, and manually redact the token line before sharing any output.Low Basis: The source's own band: LOW
0, fixed 2.97.0 (semver)2.97.0
2.97.0go get github.com/cli/cli/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0