Skip to content
Fencer Intel
high 7.2

CVE-2026-6973 kev in the critical feed json

An Improper Input Validation in Ivanti EPMM before versions 12.6.1.1, 12.7.0.1, and 12.8.0.1 allows a remotely authenticated user with admi…

published 6mo ago modified 14d ago also EUVD-2026-28396

cvss
7.2
version 3.1, CNA
cisa kev
Exploited
added 2026-05-07
epss
34.5%
EPSS 34.5% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

An Improper Input Validation in Ivanti EPMM before versions 12.6.1.1, 12.7.0.1, and 12.8.0.1 allows a remotely authenticated user with administrative access to achieve remote code execution.

Patch / fix

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.

  • Ivanti Endpoint Manager Mobile 12.6.1.1, 12.7.0.1, 12.8.0.1

Is CVE-2026-6973 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. CISA SSVC: exploitation active
  2. Added to CISA KEV
  3. Published
  4. CISA patch deadline

Known exploited

Added
6mo ago
Patch by
2026-05-10 (5mo ago)
Ransomware
Not known
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.
Vendor, product
Ivanti, Endpoint Manager Mobile (EPMM)
CISA name
Ivanti Endpoint Manager Mobile (EPMM) Improper Input Validation Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
6mo ago

Exploit prediction

34.45% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Ivanti Endpoint Manager Mobile

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.