Code execution via forged SSH conductor messages
Published Apr 18, 2026 · Updated Apr 18, 2026
Code execution in iTerm2 3.6.9 and earlier allows local users to run commands by displaying crafted terminal-control data. The Conductor parser accepts forged DCS 2000p and OSC 135 messages outside a legitimate SSH integration session, then writes predictable base64 command chunks to the local shell. Execution requires the displayed data to drive the conductor state machine and an executable attacker-controlled pathname matching a generated chunk in the working directory.
Summary
What happened
Code execution in iTerm2 3.6.9 and earlier allows local users to run commands by displaying crafted terminal-control data. The Conductor parser accepts forged DCS 2000p and OSC 135 messages outside a legitimate SSH integration session, then writes predictable base64 command chunks to the local shell. Execution requires the displayed data to drive the conductor state machine and an executable attacker-controlled pathname matching a generated chunk in the working directory.
The record
- CVE
- CVE-2026-41253
- Published
- Apr 18, 2026
- Updated
- Apr 18, 2026
- Vendor
- George Nachman
- Product
- iTerm2
- Classifications
- CWE-829, CAPEC-549, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 18, 2026CVE publishedPublication date reported by the CVE source.
- Apr 18, 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=0 <=3.6.9
What conditions does exploitation require?
What is affected?
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
- genpoc.py file-based proof of conceptproof of concept · demonstrated
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