basicsecurity.net
Proof, not just disclosure.
Threats / Ivanti / CVE-2025-4427
CVE-2025-4427 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Ivanti Endpoint Manager Mobile (EPMM) vulnerability

Ivanti Endpoint Manager Mobile (EPMM) contains an authentication bypass vulnerability in its API component that allows attackers to access protected resources without proper credentials through crafted requests.

Verdict

Today item — known-exploited.

An insecure Spring Framework implementation in EPMM's API enables unauthenticated access to protected resources. The vulnerability is actively exploited in the wild with high exploit probability, posing immediate risk to organizations running affected versions.

CISA KEV Yes · 2025-05-193EPSS 0.99589 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
344 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-19).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99589 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Ivanti, Endpoint Manager Mobile (EPMM). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-288 Auth Bypass via Alternate Path — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft malicious API requests that bypass authentication controls to gain unauthorized access to the EPMM system.
Business
Attackers gain direct access to mobile device management infrastructure, enabling potential compromise of managed endpoints and sensitive organizational data.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I enumerate and extract configuration data, user credentials, and device information from the compromised EPMM instance.
Business
Loss of confidentiality across mobile device inventory, user accounts, and enterprise security policies creates exposure for lateral movement and data exfiltration.
3

Lateral reach — past segmentation narrative 3

Attacker
I modify device policies, disable security controls, or inject malicious configurations to compromise managed mobile devices at scale.
Business
Integrity of mobile device security posture is compromised, enabling widespread endpoint compromise and potential supply chain attacks through trusted devices.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 344 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by ivanti (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ivantiCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.