Exploited CVEs / Ivanti / CVE-2026-1603

CVE-2026-1603

Ivanti Endpoint Manager (EPM) Authentication Bypass Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-03-23 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Ivanti Security Advisories, linked below.

Risk summary

HighCISA KEV
7.5
CVSS v3 base
81%
EPSS exploit probability
High
Severity
2026-03-09
Added to KEV
2026-03-23 (past due)
CISA due date

Actively exploited Ivanti Endpoint Manager (EPM) vulnerability, High severity, CVSS v3 7.5. Added to the CISA KEV catalog 2026-03-09.

Senserva AI read on CVE-2026-1603CISA required actionOfficial fix for CVE-2026-1603Admin questions

Senserva AI Opinion for CVE-2026-1603

This Ivanti EPM flaw lets a remote, unauthenticated attacker reach an alternate path that leaks specific stored credential data, meaning the real damage is credential theft that can seed follow-on attacks even after you patch. It is confirmed exploited (CISA KEV, added 2026-03-09) with an 81 percent EPSS score, so anyone running internet-reachable EPM should treat this as an active incident risk. Because EPM manages endpoints across your fleet, leaked credentials here can translate into broad administrative access.

Do this: Apply Ivanti's EPM update now, then rotate any credentials stored in or reachable through EPM in case they were already exposed.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-1603

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
The fix ships from the vendor: Ivanti Security Advisories.
Do this now: Federal remediation deadline 2026-03-23; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated September 3, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-1603

Published
2026-03-09
Last revised
2026-03-09
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when
  • 2026-03-09 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 7.5; EPSS first scored at 80.6%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-03-23 (past due).

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

Official fix for CVE-2026-1603

The authoritative fix and affected-version list are published by the vendor. Find the Endpoint Manager (EPM) advisory on Ivanti Security Advisories.

Common questions about CVE-2026-1603

Is CVE-2026-1603 actively exploited?

Yes. CVE-2026-1603 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-03-09, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 81%.

What is the CISA deadline and required action for CVE-2026-1603?

CISA set the federal (BOD 22-01) remediation due date at 2026-03-23, which has passed; treat any unremediated system as overdue. The verbatim 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.

What fixes CVE-2026-1603?

The authoritative fix is in the vendor advisory: see Ivanti Security Advisories for the patched Endpoint Manager (EPM) versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-1603?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-1603's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed once a day (early morning US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.