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

Ivanti Endpoint Manager Mobile (EPMM) vulnerability

Ivanti Endpoint Manager Mobile contains a code injection vulnerability in its API component allowing authenticated attackers to execute arbitrary code through crafted requests exploiting insecure Hibernate Validator usage.

Verdict

Today item — known-exploited.

An authenticated attacker can inject and execute arbitrary code on affected EPMM systems via malicious API requests. The vulnerability stems from improper validation handling in the Hibernate Validator integration, enabling remote code execution with active exploitation observed in the wild.

CISA KEV Yes · 2025-05-193EPSS 0.87529 (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
42 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.87529 — 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-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-94 · Code InjectionInjection
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 a malicious API request containing code injection payloads targeting the Hibernate Validator validation logic.
Business
Attackers gain remote code execution capability on mobile endpoint management infrastructure, risking complete system compromise.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I send the crafted request to the EPMM API endpoint as an authenticated user or through compromised credentials.
Business
The attack bypasses application logic controls, allowing unauthorized command execution within the trusted management platform.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with the privileges of the EPMM service process.
Business
Attackers can access sensitive mobile device management data, manipulate device policies, or pivot to connected enterprise systems.
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)
  • 42 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.