Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High ThreatIntel

High‑Severity Code Injection in Ivanti Endpoint Manager Mobile (CVE‑2026‑1340) Enables Unauthenticated RCE

Ivanti Endpoint Manager Mobile (EPMM) contains a code injection vulnerability that could allow attackers to achieve unauthenticated remote code execution.

Verisq™ Intelligence · 📅 October 07, 2026 · 📰 nvd.nist.gov
🟠
Severity
High
TI
Type
ThreatIntel
🎯
Confidence
High
🏢
Affected
3 sector(s)
✅
Actions
5 recommended
📰
Source
nvd.nist.gov

High‑Severity Code Injection in Ivanti Endpoint Manager Mobile (CVE‑2026‑1340) Enables Unauthenticated RCE

What It Is

Ivanti Endpoint Manager Mobile (EPMM) contains a code‑injection flaw that permits an attacker to inject malicious code and execute it on the server without any authentication. The vulnerability stems from insufficient input validation in a component that processes remote requests.

Exploitability

The vulnerability is classified as High severity (CVSS v3.1 base score ≈ 8.8). Public proof‑of‑concept code has been released, and the issue is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, indicating active exploitation in the wild.

Affected Products

  • Vendor: Ivanti
  • Product: Endpoint Manager Mobile (EPMM) – all supported versions prior to the forthcoming patch.

Why It Matters for Compliance & Audit Readiness

Unauthenticated remote code execution undermines the core control of access management. Organizations that rely on EPMM for mobile device lifecycle management must demonstrate that they maintain a defensible audit trail for privileged‑access controls, continuous monitoring of endpoint configurations, and evidence of timely patch management. Failure to remediate can be cited as a control weakness in audits aligned with NIST CSF, ISO 27001, and industry‑specific regulations (e.g., HIPAA, PCI‑DSS).

Recommended Actions

  • Map the control: Align the vulnerability with the “Privileged Access Management” control in your security framework and document the exposure.
  • Capture evidence: Record current EPMM version, configuration snapshots, and any existing compensating controls (e.g., network segmentation, IDS alerts).
  • Validate posture: Verify that the latest security patch from Ivanti is applied; if unavailable, implement temporary mitigations such as restricting inbound traffic to the EPMM management interface and enforcing strict input validation via a web‑application firewall.
  • Update monitoring: Add detection rules for anomalous process creation or command‑line activity associated with EPMM on your SIEM.
  • Communicate: Notify internal stakeholders and update your vendor‑risk register to reflect the elevated risk until remediation is confirmed.

Source: https://nvd.nist.gov/vuln/detail/CVE-2026-1340

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2026-1340 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →