CVE-2026-48501: GitHub CLI has an incorrect authorization header in API requests to TUF repository mirrors via `gh attestation`, `gh release verify`, and `gh release verify-asset` commands
Summary GitHub CLI incorrectly includes an authorization header in API requests to TUF repository mirrors via gh attestation, gh release verify, and gh release verify-asset commands. Affected users: - Authenticated github.com users who previously ran gh attestation commands, gh release verify, or gh release verify-asset: the github.com token was included in requests to tuf-repo.github.com, a GitHub Pages domain that…
Published May 29, 2026 · Updated Jul 30, 2026
Affected packages
github.com/cli/cli/v2
- Ecosystem
- Go
- Affected
- <= 2.92.0
- Fixed in
- 2.93.0
- Check
go list -m github.com/cli/cli/v2
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
GitHub CLI incorrectly includes an authorization header in API requests to TUF repository mirrors via gh attestation, gh release verify, and gh release verify-asset commands.
Affected users:
- Authenticated
github.comusers who previously rangh attestationcommands,gh release verify, orgh release verify-asset: thegithub.comtoken was included in requests totuf-repo.github.com, a GitHub Pages domain that is not a GitHub API endpoint. All authentication types are affected. - Users with
GH_ENTERPRISE_TOKENorGITHUB_ENTERPRISE_TOKENset who previously rangh attestationcommands,gh release verify, orgh release verify-asset: the enterprise token was included in requests to external hoststuf-repo-cdn.sigstore.devandtmaproduction.blob.core.windows.net. These hosts are not operated by GitHub.
Details
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.
Impact
Tokens were transmitted in HTTP headers to the listed hosts during normal gh attestation, gh release verify, and gh release verify-asset operations. There is no evidence that tokens were logged, retained, or accessed by unauthorized parties. If a token were captured, it would grant the same access as the token holder, potentially including private repositories, organization resources, or enterprise administration depending on token type and permissions.
Remediation and mitigation
- Revoke authentication tokens used with the GitHub CLI:
- Personal access tokens
- GitHub CLI OAuth app
- Upgrade
ghto2.93.0. - Review personal security logs and any relevant audit logs for actions associated with personal or enterprise accounts.
Credited to williammartin, BagToad, kommendorkapten, babakks, nophlyzone.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-64652
GitHub CLI partially discloses authentication tokens in `gh auth status` output
low3.3Oct 15, 2026CVE-2026-64653
GitHub CLI allows path traversal through unescaped request URL components
low2.1Oct 15, 2026CVE-2026-64655
GitHub CLI allows attestation verification bypass through unescaped regex metacharacters
low2.1Oct 15, 2026CVE-2026-45803
GitHub CLI: GitHub Actions log output in `gh run view` allows terminal escape sequence injection
low3.5No fixMay 19, 2026CVE-2025-25204
`gh attestation verify` returns incorrect exit code during verification if no attestations are present
medium6.3Feb 14, 2025CVE-2024-54132
Downloading malicious GitHub Actions workflow artifact results in path traversal vulnerability
medium6.3No fixDec 4, 2024
