Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-64655— GitHub CLI: Attestation Verification Bypass via Unescaped Regex Metacharacters in SAN Matching

Quick assessment

Affected
cli cli
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

GitHub CLI是GitHub CLI组织开源的一款命令行界面工具。 GitHub CLI 2.97.0之前版本存在输入验证错误漏洞,该漏洞源于在构建证书Subject Alternative Name匹配器时未转义正则表达式元字符,导致用户提供的仓库名或工作流名被当作正则表达式而非字面字符串处理,攻击者可通过注册相似名称绕过Sigstore证明验证,破坏供应链验证。

CVSS 2.1 · Low EPSS 0.34% · P26

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application

Affected Version Matrix 1

VendorProduct Version RangeStatus
cli cli < 2.97.0 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-64655

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
GitHub CLI: Attestation Verification Bypass via Unescaped Regex Metacharacters in SAN Matching
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
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
Source: CVE Program / CVE List V5
Vulnerability Type
不正确的正则表达式
Source: CVE Program / CVE List V5
Vulnerability Title
GitHub CLI 输入验证错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
GitHub CLI是GitHub CLI组织开源的一款命令行界面工具。 GitHub CLI 2.97.0之前版本存在输入验证错误漏洞,该漏洞源于在构建证书Subject Alternative Name匹配器时未转义正则表达式元字符,导致用户提供的仓库名或工作流名被当作正则表达式而非字面字符串处理,攻击者可通过注册相似名称绕过Sigstore证明验证,破坏供应链验证。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
cli cli < 2.97.0 -

II. Public POCs for CVE-2026-64655

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-64655

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-64655 (1)

Vendor Advisories for CVE-2026-64655 (1)

Vendor Pages for CVE-2026-64655 (1)

Same Patch Batch · cli · 2026-08-06 · 4 CVEs total

CVE-2026-64654 5.3 MEDIUM GitHub CLI: Terminal escape sequence injection in multiple `gh` commands
CVE-2026-64653 5.1 MEDIUM GitHub CLI: Unescaped variable components in request URLs could allow path traversal
CVE-2026-64652 3.3 LOW GitHub CLI: Partial token disclosure in `gh auth status` output

IV. Related Vulnerabilities

V. Comments for CVE-2026-64655

No comments yet


Leave a comment