CVE-2025-4428: Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability
Affects Ivanti Endpoint Manager Mobile (EPMM)Source CISA KEV
Mentioned vulnerabilities
Exploited in the wild · KEV due 9 Jun 2025 · public exploit available (Metasploit) · 88% EPSS : apply the vendor's fix or mitigations to Ivanti Endpoint Manager Mobile (EPMM) now.
Data as of 10/24/2026, 22:16:01 UTC
- Exploitation
Actively exploited – in CISA KEV since 05/19/2025
- KEV deadline
- 06/09/2025 US federal agencies must patch by this date; a sensible deadline for everyone else.
- EPSS
- 88.0% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Public exploits
- 1 Metasploit modulePublic attack or detection tooling exists; see Public exploits below.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HWhat to do
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Check the firmware or software version for Ivanti Endpoint Manager Mobile (EPMM) in the device's admin interface against the vendor advisory.
Public exploits and detection
Metasploit modules
Public tooling indexed from Metasploit Framework, Exploit-DB and ProjectDiscovery nuclei-templates. Its existence raises the odds of exploitation; it does not confirm attacks.
Description
Ivanti Endpoint Manager Mobile (EPMM) contains a code injection vulnerability in the API component that allows an authenticated attacker to remotely execute arbitrary code via crafted API requests. This vulnerability results from an insecure implementation of the Hibernate Validator open-source library, as represented by CVE-2025-35036.
Weaknesses
- CWE-94Improper Control of Generation of Code ('Code Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #10OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.