Quick answers
- Is CVE-2026-64653 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64653 being exploited in the wild.
- How severe is CVE-2026-64653?
- Medium severity, with a CVSS score of 4, published 6 August 2026.
- Which products and versions are affected?
- github.com/cli/cli (Go) SEMVER:introduced=0; github.com/cli/cli/v2 (Go) < 2.97.0, SEMVER:introduced=0,fixed=2.97.0.
- Is there a fix for CVE-2026-64653?
- Yes. github.com/cli/cli/v2 (Go): upgrade to 2.97.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-64653 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-64653?
- Check whether you run github.com/cli/cli (Go) or github.com/cli/cli/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/cli/cli/v2 (Go): upgrade to 2.97.0 or later
go get github.com/cli/cli/v2@v2.97.0
Technical details
The vulnerability is a path traversal / URL path injection flaw in GitHub CLI's HTTP request URL construction. Multiple commands interpolated variable path components (repository names, resource IDs, etc.) into REST API URLs without percent-encoding, allowing URL metacharacters to alter the request path and reach unintended API endpoints. The fix, released in version 2.97.0, introduced a SafeURL package that enforces percent-encoding of all variable components and rejects path-traversal patterns like ".." to prevent endpoint confusion attacks. The vulnerability requires user interaction—a user must execute a gh command that references an attacker-controlled repository or resource name.
Affected products
- GitHub CLI prior to 2.97.0
Identifiers
- CVE-2026-64653
- GHSA-4fjg-2h4q-fwg3
- GO-2026-6765
Timeline
- 2026-07-31: patched: Fixed in version 2.97.0