dbcve.org
CliApplication · GitHub

CVE-2026-48501

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to 2.93.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitHub CLI prior to 2.93.0 has a host normalization flaw in its shared HTTP client's authentication layer. The logic incorrectly treats any *.github.com subdomain (like tuf-repo.github.com) as github.com, causing the user's GitHub token to be sent to TUF repository mirrors and other external hosts accessed by gh attestation, gh release verify, and gh release verify-asset commands. The token is also forwarded to hosts that don't match github.com or known GHES instances via GH_ENTERPRISE_TOKEN fallback.

MitigationUpgrade GitHub CLI to version 2.93.0 or later to receive the corrected host detection logic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CliApplication
Affected:< 2.93.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitHub CLI version
    Run `gh --version` and compare the version number to 2.93.0
    Affected if The version shown is lower than 2.93.0 (e.g., 2.92.0, 2.80.0, etc.)
  2. Identify use of affected commands
    Review command history or logs for executions of `gh attestation`, `gh release verify`, or `gh release verify-asset`
    Affected if Any of these three commands have been run with a GitHub token present in the environment
  3. Check for active GitHub token
    Verify if the GH_TOKEN or GITHUB_TOKEN environment variable is set by running `echo $GH_TOKEN` or `echo $GITHUB_TOKEN` (the variable will be populated if a token exists)
    Affected if A GitHub token is currently set in the environment and the installed gh version is below 2.93.0
  4. Verify TUF mirror configuration
    Check if custom TUF repositories are configured by inspecting gh config list or looking for TUF_REPO_URL, TUF_ROOT, or similar environment variables
    Affected if Custom TUF repository mirrors (tuf-repo.github.com, tuf-repo-cdn.sigstore.dev, or Azure Blob Storage) are configured for use with the affected commands

A user is affected if they are running GitHub CLI version below 2.93.0 AND have used the gh attestation, gh release verify, or gh release verify-asset commands with a GitHub token present in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.93.0 or later
Fixed in 2.93.0
Interim mitigation

Upgrade GitHub CLI to version 2.93.0 or later to receive the corrected host detection logic.

Recommended fix High confidence

2.93.0

  1. Verify current gh CLI version by running: gh --version
  2. Upgrade gh CLI to version 2.93.0 or later using your package manager: For Homebrew (macOS): brew upgrade gh; For apt (Debian/Ubuntu): sudo apt update && sudo apt upgrade gh; For yum/dnf (RHEL/Fedora): sudo yum update gh or sudo dnf update gh; For Windows: winget upgrade GitHub.cli or choco upgrade gh
  3. Verify the upgrade was successful by running: gh --version
  4. Confirm the installed version is >= 2.93.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cli Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48501 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data