⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.6 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2026-1603: Authentication Bypass in Endpoint Manager

By Sai Kiran Pandrala

⚡ At a glance
SeverityCVSS 8.6 - High
Actively exploited?Yes, listed in CISA KEV (added 2026-03-09)
AffectedEndpoint Manager (see advisory for affected versions)
Fixed inSee vendor advisory
Type (CWE)CWE-288: Authentication Bypass Using an Alternate Path or Channel

Patch immediately. CISA added CVE-2026-1603 to the Known Exploited Vulnerabilities catalog on 2026-03-09. Federal civilian agencies must remediate by 2026-03-23. Treat every internet-reachable instance as a priority patch.

What is CVE-2026-1603?

CVE-2026-1603 is an Authentication Bypass flaw in Ivanti Endpoint Manager. It carries a CVSS base score of 8.6 (high). CISA confirmed real-world exploitation by adding it to the Known Exploited Vulnerabilities catalog on 2026-03-09.

From the source record: An authentication bypass in Ivanti Endpoint Manager before version 2024 SU5 allows a remote unauthenticated attacker to leak specific stored credential data.

Why it matters in practice: KEV-listed CVEs draw continuous internet-wide scanning. Any unpatched, internet-reachable installation is on borrowed time. The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Endpoint Manager matches a version listed in the Affected row above.

From the Ivanti admin console, open About / System Information and note the build number, or from a privileged shell:


show version

How to fix CVE-2026-1603

Apply the vendor patch. Target the patched build listed on the vendor advisory. The runnable command set below covers the most common deployment patterns for Endpoint Manager.

Ivanti upgrade

Apply the patched build named in the Fixed in row above via the Ivanti admin console (System -> Upgrade). For appliances:


# Vendor advisory: https://hub.ivanti.com/s/article/Security-Advisory-EPM-February-2026-for-EPM-2024?language=en_US
# From the privileged CLI
install <patched-package>.pkg
# Then reboot
reboot

After applying the patch

  1. Restart the service or device so the patched binary loads.
  2. Confirm the running version matches the Fixed in row using the verification command below.
  3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict management-plane exposure

Block public access to the admin interface at the perimeter. Allow only trusted jump hosts and bastion IPs.


# Cisco IOS example: ACL on the management VTY
configure terminal
ip access-list standard MGMT-ACL
 permit 10.10.10.0 0.0.0.255
 deny any log
line vty 0 4
 access-class MGMT-ACL in
 end
write memory

On Linux jump hosts in front of the appliance, drop traffic from anything outside the admin range:


sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

Run the product's --version or about command and compare against the Fixed in row (See vendor advisory). Re-run an authenticated vulnerability scan and confirm the scanner no longer flags CVE-2026-1603.

Also worth doing: pull recent log windows for any indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-1603 being exploited in the wild?

Yes. CISA added CVE-2026-1603 to the Known Exploited Vulnerabilities catalog on 2026-03-09. KEV listing means at least one confirmed real-world exploitation report exists.

Do I have to take downtime to patch?

For most Ivanti Endpoint Manager deployments, the patched build needs a service restart or device reboot. HA pairs and clusters can roll the upgrade by patching the standby first, failing over, then patching the former primary.

Will a WAF or IDS rule alone close CVE-2026-1603?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

How quickly should I act on CVE-2026-1603?

Within the standard patch cycle if the asset is internal-only. Inside one to two weeks for any internet-facing instance, sooner if compensating controls are not in place.

References

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*