CVE-2026-64655
LowCVSS 2.1Exploitation Probability (EPSS)
Low risk26th percentile - higher than 26% of all known CVEs
Summary
GitHub CLI before 2.97.0 fails to escape regex metacharacters in --signer-repo and --signer-workflow, allowing attackers to bypass Sigstore attestation verification with lookalike names.
Risk Assessment
Risk of supply chain compromise in CI/CD pipelines that pin trust to specific signing workflows.
Recommendation
Upgrade GitHub CLI to version 2.97.0 or later.
Other vulnerabilities in GitHub CLI
See all- CVE-2026-72924Low
GitHub CLI (gh) versions 2.28.0 through 2.97.0 bind the local listener created by gh codespace ports forward to all available network interfaces by default. While port forwarding is active, a service in a Codespace can become reachable through the user's non-loopback local IP addresses. This issue is fixed in version 2.98.0.
- CVE-2026-64654Medium
GitHub CLI (gh) is GitHub's official command line tool. Prior to version 2.97.0, multiple GitHub CLI commands printed externally controlled gist, API, pull request, release, codespace, skill, or agent-task content without neutralizing terminal escape sequences. An attacker who can influence that content can embed escape sequences that are interpreted by the terminal of a user who runs an affected command, with impact ranging from cosmetic manipulation of the title or on-screen content to, on some terminal emulators, command execution. This issue is fixed in version 2.97.0.
- CVE-2026-64653Medium
GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.97.0, some HTTP request URLs interpolate variable path components without percent encoding, allowing URL path metacharacters in attacker-controlled repository or resource values to make gh address a different API endpoint or resource than the user intended. This issue is fixed in version 2.97.0.
- CVE-2026-64652Low
GitHub CLI before 2.97.0 masks only part of certain tokens in gh auth status, potentially exposing token fragments in terminal or CI output.
- CVE-2026-59831Medium
A vulnerability in GitHub CLI (gh) from version 2.10.0 through 2.95.0 allows arbitrary command execution when connecting to a malicious Codespace using the `gh codespace jupyter` command. The command opens a JupyterLab URL supplied by a process inside the Codespace without validating that it is a loopback HTTP or HTTPS address, allowing a crafted `vscode://` or `vscode-insiders://` URL to be handed to VS Code.
- CVE-2026-48501High
GitHub CLI (gh) prior to version 2.93.0 incorrectly includes authorization headers in API requests to TUF repository mirrors. A host normalization flaw causes user tokens to be sent to external servers like tuf-repo.github.com, posing a security risk.
Original NVD description (English source)
GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.97.0, gh attestation verify builds the certificate Subject Alternative Name matcher from the --signer-repo and --signer-workflow flag values without escaping regex metacharacters, so a user-supplied repository or workflow name is treated as a regular expression rather than a literal string. Because GitHub permits characters such as `.` in organization, repository, and workflow path names and `.` is a regex wildcard, an attacker can register a lookalike name (for example github/artifact.attestations-workflows) that satisfies a matcher intended for a different trusted signer (github/artifact-attestations-workflows), bypassing the intended Sigstore attestation verification. Exploitation requires the attacker to create a plausible lookalike repository and produce valid attestations from it, which could undermine supply chain verification for CI/CD pipelines or policy gates that pin trust to a specific signing workflow. This issue is fixed in version 2.97.0.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS