Live › vulnerability › CVE-2026-64655
Go to dashboardThe GitHub CLI's attestation verify command treats the --signer-repo and --signer-workflow values as regular expressions, so a dot in a name matches any character. An attacker who registers a lookalike repository or workflow name can get a signed attestation accepted as coming from a trusted signer.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| github.com/cli/cli | go | all versions | – |
| github.com/cli/cli/v2 | go | < 2.97.0 | 2.97.0 |
2.97.0 are affectedUpgrade gh to 2.97.0 or later; for the Go module, github.com/cli/cli/v2 at 2.97.0 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-64655")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.