CVE-2026-1340

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-04-08), 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: MetasploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.
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.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation sooner than your standard update timelines at low mission impact and as soon as possible at medium or high, and watch the vendor's advisory for the fix.

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://hub.ivanti.com/s/article/Security-Advisory-Ivanti-Endpoint-Manager-Mobile-EPMM-CVE-2026-1281-CVE-2026-1340?language=en_US · https://support.mobileiron.com/mi/vsp/AB1786671/ivanti-security-update-1761642-1.1.0S-5.noarch.rpm · https://support.mobileiron.com/mi/vsp/AB1786671/ivanti-security-update-1761642-1.1.0L-5.noarch.rpm · https://nvd.nist.gov/vuln/detail/CVE-2026-1340

Published

January 29, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Oct 13, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet. Sources: cisa.
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-1340

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 187× 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 100 of 1,032 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. None are among the latest 100 rows. The 932 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(2 references)

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

  • 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-1340.yaml
    Published Sep 18, 2026

    Ivanti EPMM < 12.8.0.0 - Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2026-1340?
CVE-2026-1340 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-1340 published?
The CVE record for CVE-2026-1340 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-1340 actively exploited?
Yes. CISA added CVE-2026-1340 to the Known Exploited Vulnerabilities catalog on April 8, 2026, affecting Ivanti Endpoint Manager Mobile (EPMM). KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2026-1340?
CVE-2026-1340 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2026-1340?
CVE-2026-1340 affects Ivanti Endpoint Manager Mobile (EPMM).
How do I remediate CVE-2026-1340?
No fix for CVE-2026-1340 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-1340?

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