{"items":[{"id":"NVI-00011988","kind":"vulnerability","title":"GitHub CLI allows attestation verification bypass through unescaped regex metacharacters","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mm27-mwq9-fr5g","CVE-2026-64655"],"plain_summary":"GitHub lists this reviewed advisory for github.com/cli/cli/v2. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-7bebc47920413622d3b7469f73cf1778"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-7bebc47920413622d3b7469f73cf1778","url":"https://github.com/advisories/GHSA-mm27-mwq9-fr5g","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mm27-mwq9-fr5g","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T23:14:22.124Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-7bebc47920413622d3b7469f73cf1778"],"technology":"github.com/cli/cli/v2","known_exclusions":[],"conditions_summary":"### 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","public_affected_ranges":["< 2.97.0"]}],"null_published_at":"2026-11-01T01:03:56.620Z","source_updated_at":"2026-10-15T18:08:23.000Z","source_disclosed_at":"2026-10-15T18:08:20.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T23:14:22.124Z"}],"next_cursor":null,"snapshot_revision":"42594"}