GitHub CLI previously incorrectly attached the user's authorization token to HTTP requests sent to certain hosts during attestation and release verification commands. The client's host‑normalization logic collapsed any *.github.com subdomain to github.com, causing tokens to be sent to external domains such as tuf‑repo.github.com and tuf‑repo‑cdn.sigstore.dev. The compromised token was therefore exposed to third‑party servers that should not have received it, which is an information‑exposure flaw (CWE-551) and also a missing‑authorization flaw (CWE-863). This allowed an attacker who could observe the traffic or run the vulnerable CLI to obtain a bearer token and impersonate the user on GitHub.

Versions of the GitHub CLI (gh) prior to 2.93.0 are affected. The product is the official GitHub command‑line interface. Users running commands such as gh attestation, gh release verify, or gh release verify-asset before the fix may have sent their authentication tokens to unintended hosts.

The CVSS score of 7.4 classifies it as high severity; the EPSS score is less than 1%, and it is not listed in the CISA KEV catalog. The flaw can be exploited locally; an attacker needs remote access to the user's machine or the ability to view outbound traffic to trigger the vulnerable commands or capture the leaked token. Once captured, the token can be used to perform unauthorized actions on GitHub, constituting both an information‑exposure and a missing‑authorization vulnerability.