CVE-2026-64652
LowCVSS 3.3Exploitation Probability (EPSS)
Low risk2th percentile - higher than 2% of all known CVEs
Summary
GitHub CLI before 2.97.0 masks only part of certain tokens in gh auth status, potentially exposing token fragments in terminal or CI output.
Risk Assessment
Risk of sensitive token leakage into logs that may be shared, leading to unauthorized access.
Recommendation
Upgrade GitHub CLI to 2.97.0 and avoid sharing logs containing tokens.
Other vulnerabilities in GitHub CLI
See all- CVE-2026-72924Low
GitHub CLI (gh) versions 2.28.0 through 2.97.0 bind the local listener created by gh codespace ports forward to all available network interfaces by default. While port forwarding is active, a service in a Codespace can become reachable through the user's non-loopback local IP addresses. This issue is fixed in version 2.98.0.
- CVE-2026-64655Low
GitHub CLI before 2.97.0 fails to escape regex metacharacters in --signer-repo and --signer-workflow, allowing attackers to bypass Sigstore attestation verification with lookalike names.
- CVE-2026-64654Medium
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 issue is fixed in version 2.97.0.
- CVE-2026-64653Medium
GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.97.0, some HTTP request URLs interpolate variable path components without percent encoding, allowing URL path metacharacters in attacker-controlled repository or resource values to make gh address a different API endpoint or resource than the user intended. This issue is fixed in version 2.97.0.
- CVE-2026-59831Medium
A vulnerability in GitHub CLI (gh) from version 2.10.0 through 2.95.0 allows arbitrary command execution when connecting to a malicious Codespace using the `gh codespace jupyter` command. The command opens a JupyterLab URL supplied by a process inside the Codespace without validating that it is a loopback HTTP or HTTPS address, allowing a crafted `vscode://` or `vscode-insiders://` URL to be handed to VS Code.
- CVE-2026-48501High
GitHub CLI (gh) prior to version 2.93.0 incorrectly includes authorization headers in API requests to TUF repository mirrors. A host normalization flaw causes user tokens to be sent to external servers like tuf-repo.github.com, posing a security risk.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS