Product
iterm2
12 known vulnerabilities across versions
Vulnerabilities are listed by affected version. Select any CVE for the full briefing and its intelligence graph.
CVE-2026-41253
CVE-2025-22275
CVE-2024-38396
CVE-2024-38395
CVE-2023-46322
CVE-2023-46321
CVE-2023-46301
CVE-2023-46300
CVE-2022-45872
CVE-2019-19022
CVE-2019-9535
CVE-2015-9231
<= 3.6.9
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
>= 3.5.6 and < 3.5.11
iTerm2 3.5.6 through 3.5.10 before 3.5.11 sometimes allows remote attackers to obtain sensitive information from terminal commands
>= 3.5.0 and < 3.5.2
An issue was discovered in iTerm2 3.5.x before 3.5.2. Unfiltered use of an escape sequence to report a window title, in combinatio
>= 3.5.0 and < 3.5.2
In iTerm2 before 3.5.2, the "Terminal may report window title" setting is not honored, and thus remote code execution might occur
<= 3.4.21
iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize ssh hostnames in URLs. The hostname's initial character may
<= 3.4.21
iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize paths in x-man-page URLs. They may have shell metacharacters
< 3.4.20
iTerm2 before 3.4.20 allow (potentially remote) code execution because of mishandling of certain escape sequences related to uploa
< 3.4.20
iTerm2 before 3.4.20 allow (potentially remote) code execution because of mishandling of certain escape sequences related to tmux
< 3.4.18
iTerm2 before 3.4.18 mishandles a DECRQSS response.
<= 3.3.6
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plis
<= 3.3.5
A vulnerability exists in the way that iTerm2 integrates with tmux's control mode, which may allow an attacker to execute arbitrar
all versions
iTerm2 3.x before 3.1.1 allows remote attackers to discover passwords by reading DNS queries. A new (default) feature was added to