Ivanti
CPE vendor key: ivanti ·
203 CVEs published in the last 24 months.
CVEs (365 d)
37
▼ -8 vs prior 30d
Avg CVSS (365 d)
8.35
over 37 CVEs
Avg EPSS pct (365 d)
0.69
higher = more likely exploited
KEV hit rate (365 d)
16.2%
6 of 37 added to CISA KEV
LLM-credited CVEs
0
none detected
Monthly CVE volume — last 24 months
Each point is one calendar month. Bars in the
severity card to the right slice the same volume by CVSS band.
Severity mix
Stacked by CVSS band (Critical / High / Medium /
Low) using the best available metric per CVE.
Top affected products (24 mo)
69
56
49
16
16
15
12
12
9
6
Distinct CVEs that include each product in their
CPE configuration.
Top CWEs (24 mo)
32
15
13
11
11
9
8
8
7
7
Distinct CVEs assigned each weakness.
Recent CISA KEV adds (last 12 months)
| Added | CVE | Product | KEV name |
|---|---|---|---|
| 2026-10-13 | CVE-2026-104935 | Connect Secure | Ivanti Connect Secure Authentication Bypass by Spoofing Vulnerability |
| 2026-06-11 | CVE-2026-10520 | Sentry | Ivanti Sentry OS Command Injection Vulnerability |
| 2026-05-07 | CVE-2026-6973 | Endpoint Manager Mobile (EPMM) | Ivanti Endpoint Manager Mobile (EPMM) Improper Input Validation Vulnerability |
| 2026-04-08 | CVE-2026-1340 | Endpoint Manager Mobile (EPMM) | Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability |
| 2026-03-09 | CVE-2026-1603 | Endpoint Manager (EPM) | Ivanti Endpoint Manager (EPM) Authentication Bypass Vulnerability |
| 2026-01-29 | CVE-2026-1281 | Endpoint Manager Mobile (EPMM) | Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability |
Filtered to KEV entries whose CISA vendor or product name matches this
vendor exactly, to drop cross-OS noise (e.g. third-party Windows apps
that CPE-map to Microsoft).
Known exploited, all time (36)
| Published | CVE |
|---|---|
| 2026-10-13 | CVE-2026-104935 |
| 2026-06-09 | CVE-2026-10520 |
| 2026-05-07 | CVE-2026-6973 |
| 2026-02-10 | CVE-2026-1603 |
| 2026-01-29 | CVE-2026-1281 |
| 2026-01-29 | CVE-2026-1340 |
| 2025-05-13 | CVE-2025-4427 |
| 2025-05-13 | CVE-2025-4428 |
| 2025-04-03 | CVE-2025-22457 |
| 2025-01-14 | CVE-2024-13159 |
| 2025-01-14 | CVE-2024-13160 |
| 2025-01-14 | CVE-2024-13161 |
| 2025-01-08 | CVE-2025-0282 |
| 2024-10-08 | CVE-2024-9379 |
| 2024-10-08 | CVE-2024-9380 |
| 2024-09-19 | CVE-2024-8963 |
| 2024-09-10 | CVE-2024-8190 |
| 2024-08-13 | CVE-2024-7593 |
| 2024-05-31 | CVE-2024-29824 |
| 2024-01-31 | CVE-2024-21893 |
| 2024-01-12 | CVE-2023-46805 |
| 2024-01-12 | CVE-2024-21887 |
| 2023-08-21 | CVE-2023-38035 |
| 2023-08-15 | CVE-2023-35082 |
| 2023-08-03 | CVE-2023-35081 |
| 2023-07-25 | CVE-2023-35078 |
| 2021-12-08 | CVE-2021-44529 |
| 2021-05-27 | CVE-2021-22894 |
| 2021-05-27 | CVE-2021-22899 |
| 2021-05-27 | CVE-2021-22900 |
| 2021-04-23 | CVE-2021-22893 |
| 2020-10-28 | CVE-2020-8260 |
| 2020-09-30 | CVE-2020-8243 |
| 2020-07-30 | CVE-2020-8218 |
| 2019-05-08 | CVE-2019-11510 |
| 2019-04-26 | CVE-2019-11539 |
Attributed by CPE rather than by CISA's vendor name, so it includes
CVEs filed under another vendor whose affected-product list names this
one — shared library code is the usual reason. Broader, and
noisier, than the name-matched card above on purpose.
Generated 16 October 2026 14:24 UTC .