CVE-2025-10243: OS Command Injection in Ivanti Endpoint Manager Mobile

21

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 20.4% (30-day exploitation probability)+15
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

20.35%

ahead of 97% of scored CVEs · Oct 14, 2026

Affects

Ivanti

Endpoint Manager Mobile

CVSS base

7.2

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Ivanti Endpoint Manager Mobile).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Ivanti	Endpoint Manager Mobile	< 12.4.0.4≥ 12.5.0.0 and < 12.5.0.4≥ 12.6.0.0 and < 12.6.0.2	Vulnerable	NIST National Vulnerability Database
Ivanti	Endpoint Manager Mobile	versions not specified by the source	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.2	CVSS 3.1	High	1.2	5.9	3c1d8aa1-5a33-4ea4-8992-aadd6440af75 via NIST National Vulnerability Database
7.2	CVSS 3.1	High	—	—	ivanti via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 3c1d8aa1-5a33-4ea4-8992-aadd6440af75)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 20.35%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · ivanti/endpoint manager mobile
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 7.2
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
2025
CVE published
Oct 14, 2025 · ivanti

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

forums.ivanti.com/s/article/Security-Advisory-Endpoint-Manager-Mobile-EPMM-10-2025-Mult
Vendor Advisory, NIST National Vulnerability Database

Elsewhere on this site

Ivanti
every CVE for this vendor

Injection
same class

CWE-78
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-18851 Missing Authorization in Ivanti Endpoint Manager Mobile Sep 8, 2026
High CVE-2026-10727 OS Command Injection in Ivanti Endpoint Manager Mobile Jun 9, 2026
High CVE-2026-6973 Ivanti Endpoint Manager Mobile (EPMM) Improper Input Validation Vulnerability KEV May 7, 2026
Critical CVE-2026-7821 Improper Certificate Validation in Ivanti Endpoint Manager Mobile May 7, 2026
Critical CVE-2026-5787 Improper Certificate Validation in Ivanti Endpoint Manager Mobile May 7, 2026
High CVE-2026-5786 Improper Access Control in Ivanti Endpoint Manager Mobile May 7, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-10243 is "OS Command Injection in Ivanti Endpoint Manager Mobile", rated High. It affects Endpoint Manager Mobile (Ivanti); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 20.35% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.