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.
CVE-2026-48501
This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EPSS
- 20.8%
- KEV
- Not listed
Published
May 29, 2026
Last Modified
June 3, 2026
Advisory Details (1)
Auto-updated Jun 9, 2026Incorrect authorization header in API requests to TUF repository mirrors via `gh attestation`, `gh release verify`, and `gh release verify-asset` commands · Advisory · cli/cli · GitHub
https://github.com/cli/cli/security/advisories/GHSA-8xvp-7hj6-mcj9Vendor Advisories for CVE-2026-48501(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/cli/cli/v2 | — | 2.93.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 91× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 181 total refreshes for this CVE.
- 2026-07-16 10:06 UTCEG score recompute
- 2026-07-16 02:00 UTCEG score recompute
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 18:30 UTCEG score recompute
- 2026-07-14 14:15 UTCEG score recompute
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 01:53 UTCEG score recompute
- 2026-07-11 21:42 UTCEG score recompute
- 2026-07-11 17:35 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 22:43 UTCEG score recompute
- 2026-07-08 17:26 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-03 00:12 UTCEG score recompute
- 2026-07-02 20:05 UTCEG score recompute
- 2026-07-02 14:08 UTCEG score recompute
- 2026-07-02 09:26 UTCEG score recompute
Show 75 moreShow fewer
- 2026-07-02 04:30 UTCEG score recompute
- 2026-07-01 18:55 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 13:06 UTCEG score recompute
- 2026-07-01 08:39 UTCEG score recompute
- 2026-07-01 01:35 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 05:43 UTCEG score recompute
- 2026-06-30 01:06 UTCEG score recompute
- 2026-06-29 19:35 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 13:06 UTCEG score recompute
- 2026-06-29 00:18 UTCEG score recompute
- 2026-06-28 20:08 UTCEG score recompute
- 2026-06-28 16:00 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 10:44 UTCEG score recompute
- 2026-06-28 06:34 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 02:16 UTCEG score recompute
- 2026-06-27 22:05 UTCEG score recompute
- 2026-06-27 17:58 UTCEG score recompute
- 2026-06-27 13:47 UTCEG score recompute
- 2026-06-27 09:39 UTCEG score recompute
- 2026-06-27 05:31 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 01:24 UTCEG score recompute
- 2026-06-26 20:26 UTCEG score recompute
- 2026-06-26 16:19 UTCEG score recompute
- 2026-06-26 03:58 UTCEG score recompute
- 2026-06-25 23:49 UTCEG score recompute
- 2026-06-25 19:41 UTCEG score recompute
- 2026-06-25 15:34 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 11:20 UTCEG score recompute
- 2026-06-25 07:13 UTCEG score recompute
- 2026-06-25 03:01 UTCEG score recompute
- 2026-06-24 22:35 UTCEG score recompute
- 2026-06-24 15:25 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-18 22:28 UTCEG score recompute
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 10:25 UTCEG score recompute
- 2026-06-18 01:59 UTCEG score recompute
- 2026-06-17 21:51 UTCEG score recompute
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 17:44 UTCEG score recompute
- 2026-06-17 11:50 UTCEG score recompute
- 2026-06-17 07:43 UTCEG score recompute
- 2026-06-17 03:36 UTCEG score recompute
- 2026-06-16 23:29 UTCEG score recompute
- 2026-06-16 19:22 UTCEG score recompute
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 15:15 UTCEG score recompute
- 2026-06-16 09:38 UTCEG score recompute
- 2026-06-16 05:31 UTCEG score recompute
- 2026-06-16 01:24 UTCEG score recompute
- 2026-06-15 21:14 UTCEG score recompute
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 16:35 UTCEG score recompute
- 2026-06-15 12:27 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-48501?
When was CVE-2026-48501 disclosed?
Is CVE-2026-48501 actively exploited?
What is the CVSS score of CVE-2026-48501?
How do I remediate CVE-2026-48501?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48501
Is Your Infrastructure Affected by CVE-2026-48501?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.