{"answers":{"affected":"4 open source packages ship an affected version, including github.com/cli/cli/v2 and github.com/cli/cli.","exploited":"There is no known exploitation of CVE-2026-64655 in the wild and no public exploit code.","fix":"Upgrade github.com/cli/cli/v2 to 2.97.0 or later.","what":"CVE-2026-64655 is a low-severity vulnerability in cli, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-64655 and fix it if it is affected.\n\nWhat it is: CVE-2026-64655 is a low-severity vulnerability in cli, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-64655 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/cli/cli/v2 (Go): affected all versions; fixed in 2.97.0\n- github.com/cli/cli/v2 (Go): affected all versions; fixed in 2.97.0\n- github.com/cli/cli/v2 (Go): affected all versions; fixed in 2.97.0\n- github.com/cli/cli (Go): affected all versions; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-64655/ (Markdown: https://insights.sbomify.com/CVE-2026-64655/index.md)","id":"CVE-2026-64655","markdown":"https://insights.sbomify.com/CVE-2026-64655/index.md","name":"CVE-2026-64655","record":{"aliases":["AZL-95472","DEBIAN-CVE-2026-64655","GHSA-mm27-mwq9-fr5g","GO-2026-6767","MINI-2q9m-9fv3-75r5","MINI-6vrj-m5jq-28jp","UBUNTU-CVE-2026-64655"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub CLI","requires_auth":"none","summary":"Attackers can bypass GitHub CLI attestation verification by using regex metacharacters in signer names, undermining supply chain security for CI/CD pipelines.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-185","name":"Incorrect Regular Expression"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"GitHub CLI: Attestation Verification Bypass via Unescaped Regex Metacharacters in SAN Matching","id":"CVE-2026-64655","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"Budibase: Database Connector SQL Injections in PostgreSQL, MS SQL, and MySQL","id":"CVE-2026-64657"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/cli/cli","purl":"pkg:golang/github.com/cli/cli","source":"GO-2026-6767"},{"ecosystem":"Go","fixed":["2.97.0"],"introduced":["0"],"last_affected":[],"package":"github.com/cli/cli/v2","purl":null,"source":"GHSA-mm27-mwq9-fr5g"},{"ecosystem":"Go","fixed":["2.97.0"],"introduced":["0"],"last_affected":[],"package":"github.com/cli/cli/v2","purl":"pkg:golang/github.com/cli/cli/v2","source":"GHSA-mm27-mwq9-fr5g"},{"ecosystem":"Go","fixed":["2.97.0"],"introduced":["0"],"last_affected":[],"package":"github.com/cli/cli/v2","purl":"pkg:golang/github.com/cli/cli/v2","source":"GO-2026-6767"}],"prev":{"headline":"GitHub CLI: Terminal escape sequence injection in multiple `gh` commands","id":"CVE-2026-64654"},"products":["cli"],"published":"2026-08-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-08","vendors":["cli"]},"summary":"Attackers can bypass GitHub CLI attestation verification by using regex metacharacters in signer names, undermining supply chain security for CI/CD pipelines.","url":"https://insights.sbomify.com/CVE-2026-64655/"}