CVE-2026-64655: Github.com/cli/cli/v2 GitHub CLI Allows Attestation Verification Vulnerability

LOW
Advisory Identifier: GHSA-mm27-mwq9-fr5g
CWE-185
Published
Advisory Summary

CVE-2026-64655 is a LOW github cli allows attestation verification vulnerability (CWE-185: Incorrect Regular Expression) affecting Github.com/cli/cli/v2 libraries in the Go ecosystem. The issue involves github cli allows attestation verification bypass through unescaped regex metacharacters. Remediation is available by upgrading affected packages to version 2.97.0.

CVE-2026-64655 at a Glance

CVE Identifier CVE-2026-64655
GHSA Identifier GHSA-mm27-mwq9-fr5g
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-185: Incorrect Regular Expression
Affected Product Github.com/cli/cli/v2
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-64655

To remediate this vulnerability, upgrade all affected Github.com/cli/cli/v2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/cli/cli/v2 fixed: 2.97.0
Upgrade github.com/cli/cli/v2 to 2.97.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/cli/cli/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-64655, inspect your project dependencies for Github.com/cli/cli/v2:

inspect dependencies for github.com/cli/cli/v2

Analyze the terminal output to locate any version of Github.com/cli/cli/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.97.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-185: Incorrect Regular Expression, where the product specifies a regular expression in a way that causes data to be improperly matched or compared. In Github.com/cli/cli/v2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A security vulnerability has been identified in GitHub CLI that could allow attestation verification bypass when using `gh attestation verify` with `--signer-repo` or `--signer-workflow` flags. GitHub CLI builds the certificate matcher from these flag values without escaping regex metacharacters, so a repository or workflow name is treated as a regular expression rather than a literal string. GitHub permits characters such as  `.`  in organization, repository, and workflow path names, and  `.`  is a regex wildcard, so a malicious actor can create a lookalike name that satisfies a matcher intended for a different, trusted signer. ### Details GitHub CLI constructs a regular expression from the  `--signer-repo`  and  `--signer-workflow`  values and matches it against the signing certificate's SAN (Subject Alternative Name) during Sigstore attestation verification. The user-supplied value is interpolated into the pattern without escaping regex metacharacters, so any metacharacter permitted in a GitHub path is interpreted as regex syntax instead of a literal character. The most practical case is  `.` , which GitHub allows in org/repo names and is a regex wildcard meaning "any single character." For example, an attacker-controlled repository named: `github/artifact.attestations-workflows` matches a verifier configured for the trusted signer: `github/artifact-attestations-workflows` because the unescaped  `.`  in the constructed pattern matches the  `-`  in the attacker's name (and any other single character at that position). This affected the `--signer-repo` and `--signer-workflow` flags but did not affect the `--repo` and `--owner` flags which include an exact string comparison. In `v2.97.0`, the GitHub CLI escapes the user-supplied signer values before they are incorporated into the SAN matcher, so they are matched as literal strings. ### Impact The practical impact is limited, exploitation requires the attacker to create a plausible lookalike repository name and produce valid Sigstore attestations from it. This could undermine supply chain verification for CI/CD pipelines or policy gates that use these flags to pin trust to a specific signing workflow. ### Remediation and Mitigation 1. Upgrade `gh` to `v2.97.0` or later, which escapes signer values before matching. 2. As a workaround, use `--repo` or `--owner` flags instead of `--signer-repo` or `--signer-workflow` where applicable. 3. Manually inspect the signing certificate SAN in attestation output to confirm the signing workflow origin.

CVE-2026-64655 Affected Github.com/cli/cli/v2 Versions

1 component(s)
Fixed Versions:
2.97.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/cli/cli/v2
Go
< 2.97.0
2.97.0

References

Frequently Asked Questions

What is CVE-2026-64655?
CVE-2026-64655 is a security vulnerability in Github.com/cli/cli/v2 involving GitHub CLI allows attestation verification bypass through unescaped regex metacharacters under CWE-185: Incorrect Regular Expression.
Which Github.com/cli/cli/v2 versions are affected?
Affected versions include releases prior to 2.97.0 across affected packages: github.com/cli/cli/v2.
What version fixes CVE-2026-64655?
Upgrading to 2.97.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/cli/cli/v2 affected?
Yes, github.com/cli/cli/v2 is affected in releases prior to 2.97.0. Upgrade your dependency to 2.97.0 or later.
What CWE is associated with CVE-2026-64655?
CVE-2026-64655 is classified under CWE-185: Incorrect Regular Expression (The product specifies a regular expression in a way that causes data to be improperly matched or compared.).
How can I check Go dependencies for CVE-2026-64655?
Run the dependency tree command: 'inspect dependencies for github.com/cli/cli/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mm27-mwq9-fr5g",
  "modified" : "2026-10-15T18:08:20Z",
  "published" : "2026-10-15T18:08:20Z",
  "aliases" : [ "CVE-2026-64655" ],
  "summary" : "GitHub CLI allows attestation verification bypass through unescaped regex metacharacters",
  "details" : "### Summary\n\nA security vulnerability has been identified in GitHub CLI that could allow attestation verification bypass when using `gh attestation verify` with `--signer-repo` or `--signer-workflow` flags. GitHub CLI builds the certificate matcher from these flag values without escaping regex metacharacters, so a repository or workflow name is treated as a regular expression rather than a literal string. GitHub permits characters such as  `.`  in organization, repository, and workflow path names, and  `.`  is a regex wildcard, so a malicious actor can create a lookalike name that satisfies a matcher intended for a different, trusted signer.\n\n### Details\n\nGitHub CLI constructs a regular expression from the  `--signer-repo`  and  `--signer-workflow`  values and matches it against the signing certificate's SAN (Subject Alternative Name) during Sigstore attestation verification. The user-supplied value is interpolated into the pattern without escaping regex metacharacters, so any metacharacter permitted in a GitHub path is interpreted as regex syntax instead of a literal character.\n\nThe most practical case is  `.` , which GitHub allows in org/repo names and is a regex wildcard meaning \"any single character.\" For example, an attacker-controlled repository named:\n\n`github/artifact.attestations-workflows`\n\nmatches a verifier configured for the trusted signer:\n\n`github/artifact-attestations-workflows`\n\nbecause the unescaped  `.`  in the constructed pattern matches the  `-`  in the attacker's name (and any other single character at that position). This affected the `--signer-repo` and `--signer-workflow` flags but did not affect the `--repo` and `--owner` flags which include an exact string comparison.\n\nIn `v2.97.0`, the GitHub CLI escapes the user-supplied signer values before they are incorporated into the SAN matcher, so they are matched as literal strings.\n\n### Impact\n\nThe practical impact is limited, exploitation requires the attacker to create a plausible lookalike repository name and produce valid Sigstore attestations from it. This could undermine supply chain verification for CI/CD pipelines or policy gates that use these flags to pin trust to a specific signing workflow. \n\n### Remediation and Mitigation\n\n1. Upgrade `gh` to `v2.97.0` or later, which escapes signer values before matching.\n2. As a workaround, use `--repo` or `--owner` flags instead of `--signer-repo` or `--signer-workflow` where applicable.\n3. Manually inspect the signing certificate SAN in attestation output to confirm the signing workflow origin.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cli/cli/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.97.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/cli/cli/security/advisories/GHSA-mm27-mwq9-fr5g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-64655"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cli/cli/commit/55dbb4dc6b7edb10b48e3d7fc5bccd32318d1b55"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cli/cli"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cli/cli/releases/tag/v2.97.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-185" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-15T18:08:20Z",
    "nvd_published_at" : "2026-08-06T22:18:13Z"
  }
}