CVE-2026-48501: GitHub CLI (gh) is GitHub’s official command line tool

Q: How do I fix CVE-2026-48501?

cli: upgrade to 2.93.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-48501 being exploited?

CVE-2026-48501 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-48501 affect?

CVE-2026-48501 affects cli. Severity is high (CVSS 7.4). 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 comma

Q: How urgent is CVE-2026-48501?

Priority 36/100. High severity; Remotely exploitable, no login, no user action

Routine

HIGH 7.4REMOTEUPGRADE

CVE-2026-48501 is a high-severity flaw (CVSS 7.4) affecting cli. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 hos

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.4 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-863
Published	2026-05-29
Last modified	2026-07-21

Publisher (CNA): GitHub, Inc. · Vendor: github

Last updated 2026-07-21 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-29 16:16 UTCPublished CVE record published
2026-07-21 15:10 UTCUpdated Record last modified

github cli UPGRADE

Affected: < 2.93.0

Fixed in: 2.93.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy cli || rpm -q cli || cli --version

2. UPGRADE to 2.93.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cli

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cli

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-48501?

cli: upgrade to 2.93.0. Exact commands for each OS are on this page.

Is CVE-2026-48501 being exploited?

CVE-2026-48501 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-48501 affect?

CVE-2026-48501 affects cli. Severity is high (CVSS 7.4). 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 comma

How urgent is CVE-2026-48501?

Priority 36/100. High severity; Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2026-42994 CRITICAL 9.8 DOWNGRADE Bitwarden CLI 2026.4.0 from 2026-04-22T21:57Z to 2026-04-22T23:30Z, when obtained from npm, had embedded malic
CVE-2026-47671 MEDIUM 5.4 UPGRADE Nhost is an open source Firebase alternative with GraphQL
CVE-2026-45803 LOW 3.5 UPGRADE `gh` is GitHub’s official command line tool

References

← Back to latest CVEs