Ivanti Endpoint Manager (EPM) 2022 · Version Status
Ivanti Endpoint Manager (EPM) 2022 End of Life Date
Ivanti Endpoint Manager (EPM) 2022 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (hub.ivanti.com); the source of each date is on the product page.
⚠
Ivanti Endpoint Manager (EPM) 2022 is past end of life. This version no longer receives security patches. 358 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 31, 2025
358 days past EOL
Latest Release
2022
Standard release
Release Date
—
Ivanti Endpoint Manager (EPM) 2022 series
Where these dates come from
End of lifeOct 31, 2025Our catalog, built from the vendor pages · hub.ivanti.commedium · 1 source agrees End of active supportApr 30, 2024Our catalog, built from the vendor pages · hub.ivanti.commedium · 1 source agrees Customer care (support only, no fixes)Apr 30, 2026Our catalog, built from the vendor pages · hub.ivanti.commedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
It has been past its end-of-life date for 1 year.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
10/10 None available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
All Ivanti Endpoint Manager (EPM) Versions
| Version | Latest | EOL Date | Status |
| 2019.1 |
2019.1 |
Dec 31, 2021 |
EOL |
| 2020.1 |
2020.1 |
Oct 31, 2022 |
EOL |
| 2021.1 |
2021.1 |
Oct 31, 2023 |
EOL |
| → 2022 |
2022 |
Oct 31, 2025 |
EOL |
| 2024 |
2024 |
EOL |
Active |
What does Ivanti Endpoint Manager (EPM) 2022 end of life mean?
When Ivanti Endpoint Manager (EPM) 2022 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Ivanti Endpoint Manager (EPM) 2022 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Ivanti Endpoint Manager (EPM) 2024 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Ivanti Endpoint Manager (EPM) 2022 reach end of life?
Ivanti Endpoint Manager (EPM) 2022 reached end of life on October 31, 2025. This version is no longer receiving security patches.
Is Ivanti Endpoint Manager (EPM) 2022 still supported?
No. Ivanti Endpoint Manager (EPM) 2022 reached end of life on October 31, 2025 and is no longer receiving security patches.
What should I upgrade to from Ivanti Endpoint Manager (EPM) 2022?
The recommended upgrade from Ivanti Endpoint Manager (EPM) 2022 is
Ivanti Endpoint Manager (EPM) 2024 — the latest actively supported version. Check the
Ivanti Endpoint Manager (EPM) full timeline for all supported versions.
What are the security risks of running Ivanti Endpoint Manager (EPM) 2022 past EOL?
Since Ivanti Endpoint Manager (EPM) 2022 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Ivanti Endpoint Manager (EPM) should migrate immediately or implement compensating controls.