How severe is CVE-2026-41253?

CVE-2026-41253 has a CVSS 3.x base score of 6.9, rated medium severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.

Is CVE-2026-41253 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-41253?

CVE-2026-41253 affects Iterm2. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-41253?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-41253 have an EU (EUVD) identifier?

Yes. CVE-2026-41253 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-23656.

When was CVE-2026-41253 published?

CVE-2026-41253 was published on 2026-04-18 and last updated on 2026-06-17.

CVE-2026-41253

CVE-2026-41253 is a medium-severity vulnerability in Iterm2 with a CVSS 3.x base score of 6.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-829.

Key facts

Severity: Medium (CVSS 3.x base score 6.9)
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-23656
Weakness: CWE-829
Affected product: Iterm2
Published: 2026-04-18
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is 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 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.
How severe is CVE-2026-41253?: CVE-2026-41253 has a CVSS 3.x base score of 6.9, rated medium severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.
Is CVE-2026-41253 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-41253?: CVE-2026-41253 affects Iterm2. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-41253?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-41253 have an EU (EUVD) identifier?: Yes. CVE-2026-41253 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-23656.
When was CVE-2026-41253 published?: CVE-2026-41253 was published on 2026-04-18 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:iterm2:iterm2:*:*:*:*:*:*:*:*

More vulnerabilities in Iterm2

CVE-2024-38396 — Critical (CVSS 9.8): 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…
CVE-2024-38395 — Critical (CVSS 9.8): In iTerm2 before 3.5.2, the "Terminal may report window title" setting is not honored, and thus remote code execution…
CVE-2023-46322 — Critical (CVSS 9.8): iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize ssh hostnames in URLs. The hostname's initial…
CVE-2023-46321 — Critical (CVSS 9.8): iTermSessionLauncher.m in iTerm2 before 3.5.0beta12 does not sanitize paths in x-man-page URLs. They may have shell…
CVE-2023-46301 — Critical (CVSS 9.8): iTerm2 before 3.4.20 allow (potentially remote) code execution because of mishandling of certain escape sequences…
CVE-2023-46300 — Critical (CVSS 9.8): iTerm2 before 3.4.20 allow (potentially remote) code execution because of mishandling of certain escape sequences…

All CVEs affecting Iterm2 →

Other CWE-829 vulnerabilities

CVE-2026-1699 — Critical (CVSS 10.0): In the Eclipse Theia Website repository, the GitHub Actions workflow .github/workflows/preview.yml used…
CVE-2025-70974 — Critical (CVSS 10.0): Fastjson before 1.2.48 mishandles autoType because, when an @type key is in a JSON document, and the value of that key…
CVE-2025-0982 — Critical (CVSS 10.0): Sandbox escape in the JavaScript Task feature of Google Cloud Application Integration allows an actor to execute…
CVE-2021-41037 — Critical (CVSS 10.0): In Eclipse p2, installable units are able to alter the Eclipse Platform installation and the local machine via…
CVE-2022-1161 — Critical (CVSS 10.0): An attacker with the ability to modify a user program may change user program code on some ControlLogix, CompactLogix,…
CVE-2020-4561 — Critical (CVSS 10.0): IBM Cognos Analytics 11.0 and 11.1 DQM API allows submitting of all control requests in unauthenticated sessions. This…

Browse all CWE-829 vulnerabilities →