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

> Attackers can bypass authentication in the API to access protected resources without credentials in Ivanti Endpoint Manager Mobile.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Yes, since 19 May 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-9wcp-q959-7mq8

## What is CVE-2025-4427?

CVE-2025-4427 is a medium-severity authentication bypass vulnerability in Ivanti Endpoint Manager Mobile, published on 13 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-4427?

It affects 1 product.


Products: Ivanti Endpoint Manager Mobile.

## How do I fix CVE-2025-4427?

No fix has been published for CVE-2025-4427 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Jun 2025.

## Is CVE-2025-4427 being exploited?

Yes. Attackers have exploited CVE-2025-4427 in the wild since at least 19 May 2025.

Public exploit code:

- https://github.com/watchtowrlabs/watchTowr-vs-Ivanti-EPMM-CVE-2025-4427-CVE-2025-4428 (github_poc): https://github.com/watchtowrlabs/watchTowr-vs-Ivanti-EPMM-CVE-2025-4427-CVE-2025-4428
- Ivanti EPMM Authentication Bypass for Expression Language Remote Code Execution (metasploit)
- Ivanti Endpoint Manager Mobile 12.5.0.0 - Authentication Bypass (exploitdb)
- Detection for CVE-2025-4427 and CVE-2025-4428 (github_poc): https://github.com/rxerium/CVE-2025-4427-CVE-2025-4428
- Ivanti Endpoint Manager Mobile - Unauthenticated Remote Code Execution (nuclei): http/cves/2025/CVE-2025-4427.yaml

## Other vulnerabilities in Ivanti Endpoint Manager Mobile

- [CVE-2023-35082](https://insights.sbomify.com/CVE-2023-35082/): Ivanti Endpoint Manager Mobile (EPMM) and MobileIron Core Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2023-35078](https://insights.sbomify.com/CVE-2023-35078/): Ivanti Endpoint Manager Mobile Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2026-1281](https://insights.sbomify.com/CVE-2026-1281/): Ivanti Endpoint Manager Mobile (EPMM) Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-1340](https://insights.sbomify.com/CVE-2026-1340/): Ivanti Endpoint Manager Mobile (EPMM) Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-6973](https://insights.sbomify.com/CVE-2026-6973/): Ivanti Endpoint Manager Mobile (EPMM) Improper Input Validation (high 7.2, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4427 and fix it if it is affected.

What it is: CVE-2025-4427 is a medium-severity authentication bypass vulnerability in Ivanti Endpoint Manager Mobile, published on 13 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-4427 in the wild since at least 19 May 2025.

Affected product: Ivanti Endpoint Manager Mobile. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-4427/ (Markdown: https://insights.sbomify.com/CVE-2025-4427/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4427
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4427
- OSV: https://osv.dev/vulnerability/CVE-2025-4427

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-4427/
Summaries are generated and may contain mistakes; the official description above is the record.