Exploited vulnerability

Ivanti EPMM Code Injection Remote Code Execution (CVE-2026-1281)

A critical code injection flaw in Ivanti Endpoint Manager Mobile (EPMM) that lets an attacker run code on the server without logging in.

  • On CISA KEV
CVE ID
CVE-2026-1281
CVSS
9.8 Critical (CVSS v3.1, Ivanti as CNA; NVD shows the same score as a secondary source); no CVSS 4.0 score in the record or NVD
CISA KEV
Listed
Affected product
Ivanti Endpoint Manager Mobile (EPMM) 12.7.0.0 and earlier, per NVD
Exploited
Yes
Published
29 January 2026 (CVE record and NVD); CISA KEV 29 January 2026

In short

CVE-2026-1281 is a critical code injection flaw in Ivanti Endpoint Manager Mobile (EPMM) that lets an attacker run code on the server without logging in. Ivanti rates it CVSS 3.1 9.8, and CISA added it to the KEV catalog on 29 January 2026. NVD lists EPMM up to and including 12.7.0.0 as affected.

Profile MapVulnerability
  1. CVECVE-2026-1281
  2. ProductIvanti Ivanti Endpoint Manager Mobile (EPMM) 12.7.0.0 and earlier, per NVD
  3. CISA KEVListedKnown Exploited Vulnerabilities
  4. ExploitedYesin real attacks
  5. Fix Steps5actions listedFind Every EPMM Server · Apply Ivanti's Patch

What it allows

The CVE record says a code injection in Ivanti Endpoint Manager Mobile (EPMM) lets attackers achieve "unauthenticated remote code execution." Ivanti, the CVE numbering authority, scores it CVSS 3.1 9.8 Critical. The vector is AV:N/AC:L/PR:N/UI:N, so an attacker needs only network access to the server, with no login and no user action.

The record files the flaw under CWE-94, improper control of generation of code, and CAPEC-242 code injection. It gives no further technical detail. The remote code execution glossary entry explains why this class of bug gives an attacker control of the host.

What Public Write-Ups Claim

Two GitHub repositories mention CVE-2026-1281, and both also name its sibling CVE-2026-1340. The older one was created on 7 February 2026. Its README says the bug is reachable through the /mifs/c/appstore/fob/ path and works through Bash arithmetic expansion.

That README also lists exploit scripts, reverse shell and web shell payloads, and checks for defenders. The second repository, created on 19 February 2026, describes itself as a demo target that reproduces the bug for research. These are the authors' claims, and we have not run either project.

Exploitation Signals for CVE-2026-1281

CISA added the flaw to its Known Exploited Vulnerabilities catalog on 29 January 2026, the same day the CVE record went public. We checked these public signals on 4 November 2026.

Exploit signals
  • CISA KEVYesAdded 29 January 2026 with a due date of 1 February 2026; ransomware campaign use is marked Unknown3 Nov
  • Exploitation in CISA SSVCYesExploitation active, automatable yes, technical impact total30 Jan
  • EPSSYesScore 0.98688, percentile 0.99925 on 3 November3 Nov
  • Public PoC code on GitHubYesTwo repositories, the earliest created 7 February 20264 Nov
  • Brandefense BlackholeYesOne Telegram CVE-feed post on 26 October 2026 flags a GitHub "PoC / exploit archive" for this CVE4 Nov
Verdict In CISA KEV since 29 January 2026; CISA SSVC records active exploitation

CISA's required action is to apply mitigations per the vendor's instructions or stop using the product if none exist. Its KEV notes ask owners to check all internet-facing Ivanti products for signs of compromise. Our KEV glossary entry explains what the catalog listing means.

For another Ivanti product, see our page on the Ivanti Connect Secure bypass CVE-2026-104935. It is a separate flaw with its own CVE record and fix.

Who is affected

NVD, which analyzed the record, lists Ivanti EPMM as affected up to and including 12.5.0.0, plus the individual releases 12.5.1.0, 12.6.0.0, 12.6.1.0 and 12.7.0.0. NVD last modified the entry on 17 June 2026.

EPMM versionNVD configuration
12.5.1.0Affected
12.6.0.0Affected
12.6.1.0Affected
12.7.0.0Affected
  • Affected

The CVE record marks two labels, "12.x.1.x RPM" and "12.x.0.x RPM", as unaffected. The record does not say which EPMM releases those labels cover, and it names no fixed release number. Ivanti's EPMM 12.8.0.0 release notes list CVE-2026-1281 and CVE-2026-1340 among the security vulnerabilities that release fixes.

CISA's KEV notes link two Ivanti security update RPM files for this CVE, named ivanti-security-update-1761642-1.0.0, one for the S and one for the L build. We recommend reading Ivanti's own advisory, which the CVE record links, before choosing a patch path. Our vulnerability management guide covers how to plan and verify a rollout.

Timeline

  1. 21 Jan 2026

    Ivanti reserves CVE-2026-1281.

  2. 29 Jan 2026

    The CVE record and NVD entry go public. CISA adds the CVE to KEV the same day with a due date of 1 February 2026.

  3. 30 Jan 2026

    CISA's SSVC entry records exploitation as active.

  4. 7 Feb 2026

    The earliest GitHub repository we found for the CVE is created.

  5. 17 Jun 2026

    NVD last modifies the analyzed entry.

  6. 26 Oct 2026

    A Telegram CVE feed seen by Brandefense Blackhole flags a GitHub PoC archive for this CVE.

  7. 3 Nov 2026

    EPSS scores the CVE at 0.98688.

What to do

  1. Find Every EPMM Server

    List each Ivanti EPMM instance and note which ones answer from the internet. CISA's KEV notes tell owners to check all internet-facing Ivanti products for signs of compromise.

  2. Compare Versions With the NVD List

    NVD lists 12.5.0.0 and earlier, 12.5.1.0, 12.6.0.0, 12.6.1.0 and 12.7.0.0 as affected. Treat any server on those releases as exposed until it is patched.

  3. Apply Ivanti's Patch

    Follow the Ivanti advisory that the CVE record links. CISA's KEV notes point to the ivanti-security-update-1761642-1.0.0 RPM files and tell owners to apply the vendor's mitigations.

  4. Hunt for Compromise

    Check web and system logs on each exposed server for activity before the patch date, since the flaw was in KEV from 29 January 2026. We recommend keeping a forensic copy before you rebuild a suspect server.

  5. Plan for Products Without a Fix

    CISA's required action says to stop using the product if mitigations are unavailable. Decide in advance who may retire an EPMM server that cannot be patched.

Questions

Is CVE-2026-1281 exploited?

CISA lists it in the KEV catalog, added on 29 January 2026, and its SSVC entry records exploitation as active. EPSS gave it 0.98688 on 3 November 2026. KEV marks ransomware campaign use as Unknown.

Which EPMM versions does NVD list for CVE-2026-1281?

NVD lists 12.5.0.0 and every earlier version, plus 12.5.1.0, 12.6.0.0, 12.6.1.0 and 12.7.0.0. The CVE record names no fixed release number.

Does an attacker need an account for CVE-2026-1281?

The CVE record calls it unauthenticated remote code execution, and the CVSS vector shows PR:N and UI:N. An attacker needs only network access to the EPMM server.

How is CVE-2026-1281 different from CVE-2026-1340?

Both come from one Ivanti advisory and both score 9.8. CVE-2026-1281 entered KEV on 29 January 2026 and NVD lists five release entries for it. CVE-2026-1340 entered KEV on 8 April 2026.

Sources

  1. CVE-2026-1281 Record CVE Program / Ivanti CNA
  2. CVE-2026-1281 NVD
  3. Ivanti EPMM Resolved Issues, 12.8.0.0 Ivanti
  4. Known Exploited Vulnerabilities Catalog, CVE-2026-1281 CISA
  5. Exploit Prediction Scoring System (EPSS) FIRST