Path Traversal in github.com/cli/cli/v2 (CVE-2026-64653)
Summary
Path traversal in github.com/cli/cli/v2 (CVE-2026-64653). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.97.0 or later.
Original description
The description as published by the source.
Summary
A path traversal vulnerability has been identified in the GitHub CLI where some HTTP request URLs, REST API calls in particular, were built without properly escaping their variable path components. A value containing URL path metacharacters can alter the request path and cause gh to address a different resource than intended.
Details
Not all request URLs in the codebase were built with proper escaping of their variable path components. When a component is interpolated into the path without percent encoding, and that component contains URL path metacharacters, it breaks out of its intended segment and changes the effective request path.
In 2.97.0, request URLs are constructed in a safe manner, so a variable component can no longer escape its intended segment.
Impact
An attacker who can control a value that flows into a request path can cause gh to send the request to a different API endpoint than intended. This can lead the CLI to read or act on a resource other than the one the user meant to target.
Remediation and Mitigation
- Upgrade
ghto2.97.0. - Be cautious when running
ghagainst untrusted repositories or inputs whose names you do not control.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-64653 has been found in github.com/cli/cli/v2.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/cli/cli/v2 to 2.97.0 or later.
If unsure, ask your IT team or search "github.com/cli/cli/v2 CVE-2026-64653" on the vendor's site.
CVE-2026-64653 (github.com/cli/cli/v2) — CWE-22
Patched: 2.97.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/cli/cli/v2.
Check the vendor advisory for the affected versions of github.com/cli/cli/v2.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.97.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/cli/cli/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/cli/cli/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/cli/cli/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/cli/cli/v2 to 2.97.0ステージング環境で 2.97.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-64653 gh
- Ubuntu UBUNTU-CVE-2026-64653 gh
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com