GitHub CLI (gh) is GitHub’s official command line tool. (CVE-2026-64655)
Description
GitHub CLI (gh) versions prior to 2.97.0 contain a vulnerability in the attestation verification process where user-supplied repository or workflow names are treated as regular expressions without escaping regex metacharacters. This allows an attacker to create lookalike repository or workflow names that bypass intended Sigstore attestation verification, potentially undermining supply chain verification in CI/CD pipelines. The issue is fixed in version 2.97.0.
CVSS v4.0
Affected software
pkg:deb/ubuntu/gh?arch=source&distro=jammypkg:deb/ubuntu/gh?arch=source&distro=esm-apps/noblepkg:deb/ubuntu/gh?arch=source&distro=stonkingpkg:deb/ubuntu/gh?arch=source&distro=esm-apps/resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The GitHub CLI (gh) tool before version 2.97.0 improperly constructs the certificate Subject Alternative Name matcher from the --signer-repo and --signer-workflow flags by not escaping regex metacharacters. Since GitHub allows characters like '.' in organization, repository, and workflow names, these characters act as regex wildcards. An attacker can exploit this by registering a lookalike repository or workflow name that matches the regex pattern intended for a different trusted signer, thereby bypassing Sigstore attestation verification. Exploitation requires the attacker to produce valid attestations from the lookalike repository, which could compromise supply chain trust mechanisms. This vulnerability is addressed in version 2.97.0.
Potential Impact
An attacker who can create a plausible lookalike repository and produce valid attestations from it can bypass the intended Sigstore attestation verification. This undermines supply chain verification for CI/CD pipelines or policy gates that rely on pinned trust to specific signing workflows. There is no indication of known exploits in the wild.
Mitigation Recommendations
Upgrade GitHub CLI (gh) to version 2.97.0 or later, where this issue is fixed. No other mitigation is indicated or required according to the available data.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-64655
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:22.04:LTS","Ubuntu:Pro:24.04:LTS","Ubuntu:26.10","Ubuntu:Pro:26.04:LTS"]
- Cvss Version
- 4.0
Threat ID: 6ad3f5ba2cdf04f65666284c
Added to database: 10/17/2026, 22:24:58 UTC
Last enriched: 10/18/2026, 00:12:59 UTC
Last updated: 10/18/2026, 00:12:59 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.