CVE-2026-41253: In iTerm2 through 3.6.9, displaying a .txt file can cause code execution via DCS 2000p and OSC 135 data, if th

Q: How do I fix CVE-2026-41253?

iterm2: upgrade to newer than 3.6.9. Exact commands for each OS are on this page.

Q: Is CVE-2026-41253 being exploited?

CVE-2026-41253 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-41253 affect?

CVE-2026-41253 affects iterm2. Severity is medium (CVSS 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 contains a malicious file whose name is valid output from the conductor encoding path, such as a pathname with

Q: How urgent is CVE-2026-41253?

Priority 32/100. Public exploit reference

Routine

MEDIUM 6.9UPGRADE

CVE-2026-41253 is a medium-severity flaw (CVSS 6.9) affecting iterm2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 s

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.9 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 90%)
CISA exploited list	No
Weakness	CWE-829
Published	2026-04-18
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: iterm2

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-18 06:16 UTCPublished CVE record published
2026-06-17 10:46 UTCUpdated Record last modified

iterm2 iterm2 UPGRADE

Affected: <= 3.6.9

Fixed in: newer than 3.6.9

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy iterm2 || rpm -q iterm2 || iterm2 --version

2. UPGRADE to newer than 3.6.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade iterm2

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade iterm2

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41253?

iterm2: upgrade to newer than 3.6.9. Exact commands for each OS are on this page.

Is CVE-2026-41253 being exploited?

CVE-2026-41253 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41253 affect?

CVE-2026-41253 affects iterm2. Severity is medium (CVSS 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 contains a malicious file whose name is valid output from the conductor encoding path, such as a pathname with

How urgent is CVE-2026-41253?

Priority 32/100. Public exploit reference

References

← Back to latest CVEs