# GitHub CLI allows path traversal through unescaped request URL components

Advisory record · `GHSA-4fjg-2h4q-fwg3`

- **Identifiers:** `GHSA-4fjg-2h4q-fwg3` · `CVE-2026-64653` · `GO-2026-6765`
- **State:** Confirmed
- **Severity:** CVSS 5.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 15 Oct 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Oct 2026, 18:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/cli/cli/v2` (Go): affected `<2.97.0`; fixed in `2.97.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The GitHub CLI (github.com/cli/cli/v2) versions before 2.97.0 are affected by a path traversal flaw, where some REST API request URLs were built without escaping variable path components. A value containing URL path metacharacters can change the request path, so gh may read or act on a different resource than the user intended. The source does not describe exactly what an attacker must control beyond a value that reaches a request path. Upgrade to version 2.97.0 or later.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.1 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0051, the 43rd percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4fjg-2h4q-fwg3)

## Sources

- [GitHub Advisory Database: GHSA-4fjg-2h4q-fwg3](https://github.com/advisories/GHSA-4fjg-2h4q-fwg3)
- [OSV: GHSA-4fjg-2h4q-fwg3](https://osv.dev/vulnerability/GHSA-4fjg-2h4q-fwg3)
- <https://github.com/cli/cli/security/advisories/GHSA-4fjg-2h4q-fwg3>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-64653>
- <https://github.com/cli/cli/commit/0c2eea6338a2323cfff000160b9b5a56a38d2a06>
- <https://github.com/cli/cli>
- <https://github.com/cli/cli/releases/tag/v2.97.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4fjg-2h4q-fwg3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4fjg-2h4q-fwg3/>. Everything for agents: <https://agentprime.io/llms.txt>.