IRONSMITHINTEL
MEDIUMCVSS5.3
|
Actively Exploited
|CISA KEV|CVE-2025-4427|Auth: none — unauthenticated|Reboot: required|Manual only

Ivanti Endpoint Manager Mobile (EPMM) Authentication Bypass Vulnerability (CVE-2025-4427)

Ivanti Endpoint Manager Mobile (EPMM) contains an authentication bypass vulnerability in the API component that allows an attacker to access protected resources without proper credentials via crafted API requests. This vulnerability results from an insecure implementation of the Spring Framework open-source library.

Published May 13, 2025 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve partial data exposure. Federal agencies are required to remediate by 2025-06-09 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Authentication Bypass (CWE-288) vulnerability in Ivanti Endpoint Manager Mobile (EPMM). An authentication bypass in the API component of Ivanti Endpoint Manager Mobile 12.5.0.0 and prior allows attackers to access protected resources without proper credentials via the API. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

→

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

●Network Security Team
●Firewall Administrators
●IT Security
●Running endpoint manager mobile: v < 11.12.0.5, 12.3.0.0 ≤ v < 12.3.0.2, 12.4.0.0 ≤ v < 12.4.0.2, 12.5.0.0
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-05-19 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-06-09.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2025-4427's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2025-4427↗ MSRC Advisory↗ NVD↗ Vendor Advisory