CVE-2024-38395: iterm2 · n/a
Affects iterm2Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.5.2 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.5.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade gnachman/iterm2 to 3.5.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubgnachman/iterm2pkg:github/gnachman/iterm2Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-38395, organizations and users should take the following specific actions: 1) Immediately upgrade iTerm2 to version 3.5.2 or later once the patch is officially released to ensure the "Terminal may report window title" setting is properly enforced. 2) Until a patch is available, restrict network access to iTerm2 sessions by implementing strict firewall rules and network segmentation to limit exposure to untrusted networks or users. 3) Employ endpoint detection and response (EDR) tools to monitor for suspicious process execution or anomalous terminal activity indicative of exploitation attempts. 4) Educate users about the risks of connecting to untrusted remote hosts via iTerm2 and encourage the use of secure, verified connections. 5) Regularly audit and update macOS systems and terminal applications to maintain security hygiene. 6) Consider alternative terminal emulators with robust security controls if immediate patching is not feasible. These targeted mitigations go beyond generic advice by focusing on controlling network exposure, monitoring for exploitation signs, and emphasizing timely patch management specific to iTerm2.
Description
In iTerm2 before 3.5.2, the "Terminal may report window title" setting is not honored, and thus remote code execution might occur but "is not trivially exploitable."
References
- iterm2.com/downloads.html (opens in a new tab)
- gitlab.com/gnachman/iterm2/-/commit/f1e89f78dd72dcac3ba66d3d6f93db3f7f649219 (opens in a new tab)
- openwall.com/lists/oss-security/2024/06/15/1 (opens in a new tab)
- gitlab.com/gnachman/iterm2/-/tags/v3.5.2 (opens in a new tab)
- openwall.com/lists/oss-security/2024/06/17/1 (opens in a new tab)