Arbitrary code execution via shell environment poisoning
Published Jan 14, 2026 · Updated Jan 14, 2026
Command allowlist bypass in Anysphere Cursor before 2.3 allows remote attackers to execute code through direct or indirect prompt injection. The terminal tool's command parser permits shell built-ins omitted from the allowlist to change environment variables that trusted commands consume. Exploitation requires the non-default Auto-Run and Allowlist modes and a command dependent on the poisoned environment; the resulting chain executes arbitrary code.
Summary
What happened
Command allowlist bypass in Anysphere Cursor before 2.3 allows remote attackers to execute code through direct or indirect prompt injection. The terminal tool's command parser permits shell built-ins omitted from the allowlist to change environment variables that trusted commands consume. Exploitation requires the non-default Auto-Run and Allowlist modes and a command dependent on the poisoned environment; the resulting chain executes arbitrary code.
The record
- CVE
- CVE-2026-22708
- Published
- Jan 14, 2026
- Updated
- Jan 14, 2026
- Vendor
- Anysphere
- Product
- Cursor
- Classifications
- CWE-78, CWE-269, CWE-20, CWE-77, CWE-74, CWE-94, CWE-15, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2026CVE publishedPublication date reported by the CVE source.
- Jan 14, 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.3
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