CVE-2026-1281

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-01-29), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild
9.8EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 99%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
99%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM-CVE-2026-1281-CVE-2026-1340 · https://support.mobileiron.com/mi/vsp/AB1771634/ivanti-security-update-1761642-1.0.0S-5.noarch.rpm · https://support.mobileiron.com/mi/vsp/AB1771634/ivanti-security-update-1761642-1.0.0L-5.noarch.rpm · https://nvd.nist.gov/vuln/detail/CVE-2026-1281

Published

January 29, 2026

Last Modified

October 7, 2026

Advisory Details (2)

Auto-updated Oct 14, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Fix referenced — no release confirmed yet.
Web page

Ivanti Innovators Hub

https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM-CVE-2026-1281-CVE-2026-1340
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-1281

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 169× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 906 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 808 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-16 22:55 UTCEG score recompute
  2. 2026-10-16 22:54 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-16 00:50 UTCEG score recompute
  4. 2026-10-16 00:50 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-15 02:46 UTCEG score recompute
  6. 2026-10-15 02:46 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-14 16:32 UTCEPSS rescoreEPSS 99% · 99th percentile
  8. 2026-10-14 04:43 UTCEG score recompute
  9. 2026-10-14 04:43 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-13 06:38 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-12 16:36 UTCEG score recompute
  12. 2026-10-12 08:35 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-12 04:08 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-11 23:43 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-11 19:19 UTCEG score recompute
  16. 2026-10-11 19:19 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-11 18:24 UTCEG score recompute
  18. 2026-10-11 14:55 UTCEG score recompute
  19. 2026-10-11 14:55 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-11 10:31 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-11 06:07 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-11 01:43 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-10 21:19 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-10 16:54 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-10 12:30 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 73 more
  1. 2026-10-10 08:06 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-10 03:42 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-09 23:18 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-09 18:54 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-09 14:30 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-09 10:05 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-09 05:41 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-09 01:17 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-08 20:53 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-08 16:29 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-08 12:03 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-08 07:38 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-08 03:14 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-07 22:50 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-07 18:27 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-07 14:29 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-07 10:05 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-07 05:42 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-07 01:18 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-06 20:53 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-06 16:27 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-06 12:04 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-06 07:40 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-06 03:16 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-06 03:15 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-06 03:15 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-06 03:14 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-05 22:48 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-05 18:25 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-10-05 14:02 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-05 09:38 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-05 05:15 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-05 00:51 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-04 20:28 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-04 16:04 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-04 11:40 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-04 07:17 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-04 02:53 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-03 22:29 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-03 18:04 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-03 13:40 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-03 09:15 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-03 04:51 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-03 00:27 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-02 20:03 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-02 15:39 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-02 11:16 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-02 06:51 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-02 02:27 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-01 22:03 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-01 17:39 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-01 13:13 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-01 08:49 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-01 04:26 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-01 00:02 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-09-30 19:37 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-09-30 15:14 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-30 10:50 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-09-30 06:25 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-30 02:01 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-09-29 21:37 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-29 17:09 UTCEG score recompute
  63. 2026-09-29 17:09 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-29 15:21 UTCEPSS rescoreEPSS 99% · 99th percentile
  65. 2026-09-29 12:45 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-29 08:22 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-09-29 03:58 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-28 23:33 UTCEG score recompute
  69. 2026-09-28 23:33 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-28 19:09 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-28 14:44 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-28 10:20 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-09-28 05:56 UTCGHSA enrichmentGHSA-mqp2-8ch3-3446 · GitHub severity CRITICAL · GitHub CVSS 9.8

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 2 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Metasploitexploit/linux/http/ivanti_epmm_rce✓ verified
    Published Feb 10, 2026

    Ivanti Endpoint Manager Mobile (EPMM) unauthenticated RCE

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-1281.yaml
    Published Sep 15, 2026

    Ivanti EPMM <=12.7.0.0 - Unauthenticated Code Injection

    Open source ↗
  • GitHub PoCYunfeiGE18/CVE-2026-1281-CVE-2026-1340-Ivanti-EPMM-RCE
    Published Feb 19, 2026

    A simple demo application that shows how to reproduce the Ivanti EPMM pre-auth RCE vulnerability (CVE-2026-1281 / CVE-2026-1340) for educational and security research purposes.

    Open source ↗
  • GitHub PoCMehdiLeDeaut/CVE-2026-1281-Ivanti-EPMM-RCE
    Published Feb 7, 2026

    Proof of Concept for CVE-2026-1281 & CVE-2026-1340 - Ivanti EPMM Pre-Auth RCE via Bash Arithmetic Expansion

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2026-1281?
CVE-2026-1281 is a critical-severity vulnerability; its CVE record was published on January 29, 2026. A code injection in Ivanti Endpoint Manager Mobile allowing attackers to achieve unauthenticated remote code execution.
When was the CVE record for CVE-2026-1281 published?
The CVE record for CVE-2026-1281 was published on January 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-1281 actively exploited?
Yes. CISA added CVE-2026-1281 to the Known Exploited Vulnerabilities catalog on January 29, 2026, affecting Ivanti Endpoint Manager Mobile (EPMM). KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2026-1281?
CVE-2026-1281 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2026-1281?
CVE-2026-1281 affects Ivanti Endpoint Manager Mobile (EPMM).
How do I remediate CVE-2026-1281?
A fix for CVE-2026-1281 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-1281

Explore →

Is Your Infrastructure Affected by CVE-2026-1281?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs