CVE-2026-48501
HighCVSS 7.4Exploitation Probability (EPSS)
Low risk21th percentile - higher than 21% of all known CVEs
Summary
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.
Risk Assessment
The organization risks leaking GitHub access tokens to unauthorized third parties, potentially leading to unauthorized access to repositories and data.
Recommendation
Immediately update GitHub CLI to version 2.93.0 or later, which fixes this vulnerability.
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-64652Low
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.
- 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.
Original NVD description (English source)
GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.93.0, GitHub CLI incorrectly includes authorization header in API requests to TUF repository mirrors via gh attestation, gh release verify, and gh release verify-asset commands. The CLI uses a shared HTTP client with an authentication layer that automatically attaches tokens to outgoing requests. This layer lacks accurate host detection and can incorrectly attribute the target host, providing it with a token it should never receive. Specifically, the host normalization logic collapses any *.github.com subdomain to github.com, so a request to tuf-repo.github.com (a GitHub Pages site, not a GitHub API endpoint) is treated as a request to github.com and receives the user's github.com token. For hosts that don't match github.com or a known GHES instance at all, the resolver falls back to GH_ENTERPRISE_TOKEN if set. The gh attestation, gh release verify and gh release verify-asset commands fetch data from several external hosts as part of their normal operation (TUF metadata from tuf-repo.github.com and tuf-repo-cdn.sigstore.dev, artifact bundles from Azure Blob Storage). Because these requests go through the same authenticated HTTP client, the token is sent to all of them. This vulnerability is fixed in 2.93.0.