CVE-2026-1340: Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability

Quick Answer

CISA describes CVE-2026-1340 as unauthenticated remote code execution through code injection in Ivanti EPMM. Identify the appliance release and reachable services, preserve server and off-device logs, and obtain Ivanti's exact update for this CVE. No fixed build is verified here. Do not transfer the administrative-access prerequisite of a different EPMM vulnerability to this unauthenticated path, or assume updating removes an earlier compromise.

Evidence check: The vendor evidence and its limits are described below. CISA KEV catalog 2026.10.02 was checked October 2; catalog chronology is separate from vendor publication history and evidence of compromise in your deployment. No exploit or update test is claimed.

Context

Status At A Glance

Product scope	Ivanti — Endpoint Manager Mobile (EPMM)
CVE	CVE-2026-1340
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-04-08
Vendor severity	Consult the live vendor advisory; no vendor severity is inferred from KEV status.
CVSS	Consult the live vendor advisory; no CVSS value is inferred from KEV status.
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-94
Federal remediation date	2026-04-11 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability. Ivanti Endpoint Manager Mobile (EPMM) contains a code injection vulnerability that could allow attackers to achieve unauthenticated remote code execution. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Inventory the EPMM appliance release, applied patches and service exposure. Match CVE-2026-1340 in Ivanti's paired advisory, not just the product name or a fix listed for another Ivanti management product.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Endpoint Manager Mobile (EPMM) asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Ivanti advisory.
4. Remediate. Confirm the exact product, release, exposure, and prerequisites against the live vendor advisory, then apply the vendor-listed update or mitigation. CISA added CVE-2026-1340 to KEV on 2026-04-08.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

CISA's KEV record does not mark this entry for forensic triage. That field is not proof of a clean system; consult the vendor advisory for indicators and recovery guidance.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: Ivanti's exact exploitation assessment was not recovered. CISA independently records exploitation and an April 8 KEV addition. Its forensic-triage No field does not remove the need to investigate suspicious EPMM activity.

CISA statement: CVE-2026-1340 was added to KEV on 2026-04-08. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Ivanti advisory or support notice
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2026-1340 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.