This page was not yet optimized for use on mobile devices.
CVE-2026-41253
Data
| Vulnerability ID | CVE-2026-41253 |
|---|---|
| Published on | 18.04.2026 06:16 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:iterm2:iterm2:1.0.0:*:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.0:*:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.1.1:-:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.1.1:beta:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.1.3:-:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.1.3:beta:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.1.4:*:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.9.20151111:*:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.9.20151229:*:*:*:*:*:*:*,
cpe:2.3:a:iterm2:iterm2:2.9.20160102:*:*:*:*:*:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.