CVE-2026-1603: Ivanti Endpoint Manager (EPM) Authentication Bypass Vulnerability
Tech GuruQuick Answer
CVE-2026-1603 can let a remote unauthenticated attacker disclose specific stored credential data through an alternate authentication path in Ivanti Endpoint Manager. Scope the EPM server release and exposure, preserve access evidence and identify potentially exposed credentials for incident review. This is not an EPMM notice, and no exact fixed EPM build is verified here. Installing an update does not invalidate credentials already disclosed.
Fix Or Immediate Action
What to do now: Confirm the exact product, release, exposure, and prerequisites against the live vendor advisory, then apply the vendor-listed update or mitigation. CISA added CVE-2026-1603 to KEV on 2026-03-09.
Evidence check: The vendor evidence and its limits are described below. CISA KEV catalog 2026.10.02 was checked October 2; catalog chronology is separate from vendor publication history and evidence of compromise in your deployment. No exploit or update test is claimed.
Context
Scope And Impact In Plain Language
Who should check: Anyone who manages Ivanti Endpoint Manager (EPM).
When this applies: Only when the exact product, version, and required configuration match the live vendor advisory. Owning the product family alone does not mean the device is vulnerable.
What could happen: CISA describes leakage of specific stored credential data without authentication. The description does not establish disclosure of every credential or standalone code execution.
Not sure? Find the product name and version in the device or application, then compare them with the affected-products section of the linked vendor notice.
Status At A Glance
| Product scope | Ivanti — Endpoint Manager (EPM) |
|---|---|
| CVE | CVE-2026-1603 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-03-09 |
| Vendor severity | Consult the live vendor advisory; no vendor severity is inferred from KEV status. |
| CVSS | Consult the live vendor advisory; no CVSS value is inferred from KEV status. |
| Ransomware field | Unknown — this is not the same as No; CISA has not marked the field Known. |
| Forensic-triage field | No in the current CISA field; organizations should still investigate when exposure or evidence warrants it. |
| CWE | CWE-288 |
| Federal remediation date | 2026-03-23 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
Ivanti Endpoint Manager (EPM) Authentication Bypass Vulnerability. Ivanti Endpoint Manager (EPM) contains an authentication bypass using an alternate path or channel vulnerability that could allow a remote unauthenticated attacker to leak specific stored credential data. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.
Affected Scope
Inventory Ivanti Endpoint Manager, including the installed EPM2024 update level where applicable, and its reachable authentication paths. Do not substitute Endpoint Manager Mobile release numbers or generic EPM service-update availability for a CVE-2026-1603 fix mapping.
Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.
Steps
What To Do Now
- Confirm. Inventory every Endpoint Manager (EPM) asset and record its exact version, patch level, role, relevant configuration, and exposure.
- Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
- Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Ivanti advisory.
- Remediate. Confirm the exact product, release, exposure, and prerequisites against the live vendor advisory, then apply the vendor-listed update or mitigation. CISA added CVE-2026-1603 to KEV on 2026-03-09.
- Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
- Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.
Fixed Releases And Mitigation
Permanent Fix
The exact CVE-2026-1603 fixed EPM release was not recovered from Ivanti's February advisory. Obtain its affected/fixed row and package verification instructions for the installed EPM branch. Coordinate any justified credential rotation with incident response; an update alone cannot make an already-disclosed credential secret again.
Workaround Or Temporary Mitigation
Consult the live vendor advisory for the exact affected and fixed release matrix; no release number is asserted here.
Important boundary: A workaround, access restriction, or provider-side control may reduce risk while the update is prepared, but it does not necessarily remove vulnerable code or erase an earlier compromise. Install the vendor-approved update when one is available.
Investigation And Recovery
CISA's KEV record does not mark this entry for forensic triage. That field is not proof of a clean system; consult the vendor advisory for indicators and recovery guidance.
When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.
Notes
Exploitation Evidence
Vendor statement: Ivanti's exact exploitation assessment is not established here. CISA independently records exploitation and a March 9 KEV addition; keep that evidence separate from assumptions about what an individual server disclosed.
CISA statement: CVE-2026-1603 was added to KEV on 2026-03-09. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.
Validation And Boundaries
This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.
Related TechGeeks Resources
- TechGeeks Security Notice Center
- All Security Notices
- What to Do When a Device Hits CISA KEV
- Router CVE Exposure, Version, and Mitigation Checklist
- IoT Firmware Update and End-of-Support Checklist
- Live Protect and Runtime Vulnerability Shielding
References
Wrap-Up
Record whether CVE-2026-1603 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.
Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.
