LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1281: A code injection in Ivanti Endpoint Manager Mobile allowing attackers to achieve unauthenticated remote cod...

A code injection in Ivanti Endpoint Manager Mobile allowing attackers to achieve unauthenticated remote code execution.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-1281 is a critical Ivanti Endpoint Manager Mobile flaw that could let an unauthenticated remote attacker run code on the system. For executives, this is high urgency because successful exploitation could compromise confidentiality, integrity, and availability of a mobile device management platform.

Executive priority

Treat as urgent for affected Ivanti EPMM environments. The vulnerability is unauthenticated, remote, and critical impact, but the provided sources do not confirm active exploitation. Prioritize exposure reduction and vendor-directed remediation.

Technical view

The CVE describes CWE-94 code injection in Ivanti Endpoint Manager Mobile affecting 12.x.1.x RPM and 12.x.0.x RPM versions. CVSS 3.1 is 9.8: network-reachable, low complexity, no privileges, no user interaction, with high impact across confidentiality, integrity, and availability.

Likely exposure

Organizations running Ivanti Endpoint Manager Mobile 12.x.1.x RPM or 12.x.0.x RPM are potentially exposed, especially if the service is reachable from untrusted networks. The source bundle does not provide deployment-specific exposure details.

Exploitation context

The provided CVE record states unauthenticated remote code execution is possible. The bundle marks KEV as false, so active exploitation is not confirmed by the provided sources.

Researcher notes

Public details in the bundle are limited to code injection, unauthenticated RCE, affected RPM version branches, and CVSS. Do not assume exploit availability or specific vulnerable endpoints from these sources. Consult the Ivanti advisory for authoritative technical and remediation details.

Mitigation direction

  • Identify all Ivanti Endpoint Manager Mobile deployments and versions.
  • Review the Ivanti security advisory for vendor-approved fixes or workarounds.
  • Prioritize remediation for internet-facing or externally reachable instances.
  • Restrict network access to management interfaces where operationally possible.
  • Monitor Ivanti and CISA sources for updated exploitation or remediation guidance.

Validation and detection

  • Confirm whether deployed EPMM versions match 12.x.1.x RPM or 12.x.0.x RPM.
  • Check asset inventory for externally reachable EPMM services.
  • Verify remediation status against the Ivanti advisory.
  • Review logs for unusual unauthenticated access patterns or unexpected process behavior.
  • Track CISA KEV status for any change in exploitation evidence.
Prepared
Reviewed
Confidence
medium
Sources
4

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1281 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-1281Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IvantiEndpoint Manager Mobile12.x.1.x RPM, 12.x.0.x RPMaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.