PT-2026-44905 · Github · Github Cli

Published 2026-05-29 · Updated 2026-05-29 · CVE-2026-48501

Positive Technologies (AI Summary)

CVSS v3.1

7.4

High

Base vector

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Name of the Vulnerable Software and Affected Versions GitHub CLI versions prior to 2.93.0

Description GitHub CLI incorrectly includes authorization headers in API requests to TUF repository mirrors when using the gh attestation, gh release verify, and gh release verify-asset commands. The tool utilizes a shared HTTP client with an authentication layer that automatically attaches tokens to outgoing requests but lacks accurate host detection. Specifically, the host normalization logic collapses any *.github.com subdomain to github.com, causing requests to tuf-repo.github.com (a GitHub Pages site) to be treated as requests to github.com and thus include the user's token. For hosts that do not match github.com or a known GHES instance, the resolver may fall back to using the GH ENTERPRISE TOKEN if it is set. Consequently, tokens are sent to external hosts such as tuf-repo-cdn.sigstore.dev and tmaproduction.blob.core.windows.net during normal operations.

Recommendations Update to version 2.93.0. Revoke authentication tokens used with the GitHub CLI, including Personal access tokens and GitHub CLI OAuth app authorizations. Review personal security logs and relevant audit logs for actions associated with personal or enterprise accounts.

Fix

Incorrect Authorization

Weakness Enumeration

CWE-863

Related Identifiers

CVE-2026-48501

GHSA-8XVP-7HJ6-MCJ9

Affected Products

Github Cli

References · 5

• https://osv.dev/vulnerability/GHSA-8xvp-7hj6-mcj9 · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2026-48501 · Security Note
• https://github.com/cli/cli/releases/tag/v2.93.0 · Note
• https://github.com/cli/cli/security/advisories/GHSA-8xvp-7hj6-mcj9 · Note
• https://github.com/cli/cli · Note