Host command execution via writable Git hooks
Published Feb 13, 2026 · Updated Feb 13, 2026
Missing authorization in Cursor before 2.5 allows remote authenticated users to escape the agent sandbox and execute host commands. The agent could write protected .git configuration, including hook definitions, and Git automatically ran the resulting commands when a later hook event occurred. Exploitation requires control of agent input, such as prompt injection, but no further user interaction; commands run outside the sandbox with the Cursor process's host privileges.
Summary
What happened
Missing authorization in Cursor before 2.5 allows remote authenticated users to escape the agent sandbox and execute host commands. The agent could write protected .git configuration, including hook definitions, and Git automatically ran the resulting commands when a later hook event occurred. Exploitation requires control of agent input, such as prompt injection, but no further user interaction; commands run outside the sandbox with the Cursor process's host privileges.
The record
- CVE
- CVE-2026-26268
- Published
- Feb 13, 2026
- Updated
- Feb 13, 2026
- Vendor
- Anysphere
- Product
- Cursor
- Classifications
- CWE-862, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 13, 2026CVE publishedPublication date reported by the CVE source.
- Feb 13, 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.5
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.
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