Command execution via unvalidated Jupyter server URL
Published Jul 9, 2026 · Updated Jul 9, 2026
Command execution in GitHub CLI 2.10.0 through 2.95.0 allows remote authenticated users to run code via a malicious Codespace. StartJupyterServer trusts a Codespace-supplied JupyterLab URL, which permits a vscode or vscode-insiders scheme to reach the operating system and launch VS Code. Exploitation requires the user to run gh codespace jupyter against the malicious Codespace and accept a VS Code open-URL or Workspace Trust prompt.
Summary
What happened
Command execution in GitHub CLI 2.10.0 through 2.95.0 allows remote authenticated users to run code via a malicious Codespace. StartJupyterServer trusts a Codespace-supplied JupyterLab URL, which permits a vscode or vscode-insiders scheme to reach the operating system and launch VS Code. Exploitation requires the user to run gh codespace jupyter against the malicious Codespace and accept a VS Code open-URL or Workspace Trust prompt.
The record
- CVE
- CVE-2026-59831
- Published
- Jul 9, 2026
- Updated
- Jul 9, 2026
- Vendor
- Product
- GitHub CLI
- Classifications
- CWE-20, CWE-829, T1204
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2026CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.10.0, < 2.96.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo