CVE-2026-64655
GitHub CLI (gh) is GitHub’s official command line tool. Prior to …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/cli/cli/commit/55dbb4dc6b7edb10b48e3d7fc5bccd32318d1b55
- github.com/cli/cli/releases/tag/v2.97.0
- github.com/cli/cli/security/advisories/GHSA-mm27-mwq9-fr5g
- nvd.nist.gov/vuln/detail/CVE-2026-64655
- github.com/advisories/GHSA-mm27-mwq9-fr5g
- nvd.nist.gov/vuln/detail/CVE-2026-64655
- cve.org/CVERecord?id=CVE-2026-64655
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.