Lucene search
+L

4 matches found

RedhatCVE
RedhatCVE
•added 2026/04/20 7:23 p.m.•28 views

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...

7.8CVSS6.2AI score0.00202EPSS
SaveExploits1References1
osv_cve
osv_cve
•added 2026/04/18 5:27 a.m.•28 views

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...

6.9CVSS6.2AI score0.00202EPSS
SaveExploits1References6
Cvelist
Cvelist
•added 2026/04/18 5:27 a.m.•58 views

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...

6.9CVSS0.00202EPSS
SaveExploits1References4
EUVD
EUVD
•added 2026/04/18 5:27 a.m.•26 views

EUVD-2026-23656

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...

6.9CVSS6.2AI score0.00202EPSS
SaveExploits1References4
Rows per page
Query Builder