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, enabling an adversary to impersonate the user and access GitHub resources. This flaw is categorized as CWE-863, which indicates a missing authorization requirement.

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 not available, and it is not listed in the CISA KEV catalog. The attack exploits the client locally; an attacker would need to have access to the user's environment to trigger the vulnerable commands or observe the outbound traffic. If an attacker can observe the leaked token, they could perform unauthorized actions on GitHub in the user's behalf. While exploitation is limited to systems where the vulnerable CLI is installed and used, the potential impact of credential theft is significant, warranting prompt remediation.