In iTerm2 through 3.6.9, displaying a .txt file can cause code execution via DCS 2000p and OSC 135 data, if the working directory contains a malicious file whose name is valid output from the conductor encoding path, such as a pathname with an initial ace/c+ substring, aka "hypothetical in-band signaling abuse." This occurs because iTerm2 accepts the SSH conductor protocol from terminal output that does not originate from a legitimate conductor session.
CVSS Score
6.9
EPSS Score
0.002
Published
2026-04-18
iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize paths in x-man-page URLs. They may have shell metacharacters for a /usr/bin/man command line.
CVSS Score
9.8
EPSS Score
0.007
Published
2023-10-23
iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize ssh hostnames in URLs. The hostname's initial character may be non-alphanumeric. The hostname's other characters may be outside the set of alphanumeric characters, dash, and period.
CVSS Score
9.8
EPSS Score
0.007
Published
2023-10-23
iTerm2 before 3.4.20 allow (potentially remote) code execution because of mishandling of certain escape sequences related to tmux integration.
CVSS Score
9.8
EPSS Score
0.012
Published
2023-10-22
iTerm2 before 3.4.20 allow (potentially remote) code execution because of mishandling of certain escape sequences related to upload.
CVSS Score
9.8
EPSS Score
0.012
Published
2023-10-22
iTerm2 before 3.4.18 mishandles a DECRQSS response.
CVSS Score
9.8
EPSS Score
0.009
Published
2022-11-23