{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41253 exists.","fix":"No fix has been published for CVE-2026-41253 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41253 is a medium-severity code injection vulnerability in iTerm2, published on 18 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41253 and fix it if it is affected.\n\nWhat it is: CVE-2026-41253 is a medium-severity code injection vulnerability in iTerm2, published on 18 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41253 exists.\n\nAffected product: iTerm2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41253/ (Markdown: https://insights.sbomify.com/CVE-2026-41253/index.md)","id":"CVE-2026-41253","markdown":"https://insights.sbomify.com/CVE-2026-41253/index.md","name":"CVE-2026-41253","record":{"aliases":["GHSA-5pgv-4jf4-9r43"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"macOS terminal emulator","requires_auth":"none","summary":"Attackers can execute arbitrary code in iTerm2 by tricking users into viewing a malicious text file that abuses terminal protocol signaling.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"iterm2","vendor":"iterm2"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Code injection in iTerm2","id":"CVE-2026-41253","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Integer overflow in little cms color engine","id":"CVE-2026-41254"},"packages":[],"prev":{"headline":"xrdp: lib_palette_update Heap Buffer Overflow \u0026 RCE","id":"CVE-2026-41252"},"products":["iTerm2"],"published":"2026-04-18","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-38395","kev_date_added":null,"published":"2024-06-16"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-38396","kev_date_added":null,"published":"2024-06-16"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-46300","kev_date_added":null,"published":"2023-10-22"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2023-46301","kev_date_added":null,"published":"2023-10-22"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-46321","kev_date_added":null,"published":"2023-10-22"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-46322","kev_date_added":null,"published":"2023-10-22"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2022-45872","kev_date_added":null,"published":"2022-11-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["iTerm2"]},"summary":"Attackers can execute arbitrary code in iTerm2 by tricking users into viewing a malicious text file that abuses terminal protocol signaling.","url":"https://insights.sbomify.com/CVE-2026-41253/"}