GitHub CLI (gh) allowed unescaped variable components in HTTP request URLs, enabling attackers to embed URL path metacharacters via repository or resource values. This flaw permits gh to target different GitHub API endpoints or resources than intended, potentially exposing sensitive data or enabling unauthorized actions. The weakness is a classic path traversal vulnerability as identified by CWE‑22. While the description does not state a formal exploit, it is implied that attackers can influence gh’s target endpoint through crafted input, making the attack vector reliant on control over command parameters or repository identifiers.

The issue affects the GitHub CLI (gh) product, specifically versions released prior to v2.97.0. All users running any gh upgrade before that release are vulnerable.

With a CVSS score of 5.1, the vulnerability is considered medium severity. No EPSS score is available, and it is not listed in CISA’s KEV catalog, suggesting no widespread exploitation is documented. However, the potential for unauthorized API access exists if an attacker can supply malicious repository or resource values, typically through user input or compromised scripts that invoke gh. The exploit would require the attacker to influence the command parameters that gh uses to build URLs, and the risk remains controlled by the assurance that patching the tool mitigates the flaw.