Threats / Ivanti / CVE-2026-1603
CVE-2026-1603
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Ivanti Endpoint Manager (EPM) vulnerability
Ivanti Endpoint Manager contains an authentication bypass vulnerability allowing remote unauthenticated attackers to leak stored credential data through an alternate path or channel.
Verdict
Today item — known-exploited.
A remote unauthenticated attacker can bypass authentication in Ivanti Endpoint Manager to access and exfiltrate stored credentials. The vulnerability is actively exploited in the wild, presenting immediate risk to organizations using affected versions.
CISA KEV Yes · 2026-03-095EPSS 0.8056 (verify live)6CVSS 8.63CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Public PoC / detection · nuclei template13
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
109 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-09).
Probability (EPSS)
EPSS 0.8056 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) · Affected: Ivanti, Endpoint Manager (EPM). Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-288 Auth Bypass via Alternate Path — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 27 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that Ivanti Endpoint Manager accepts requests through an alternate authentication path that does not enforce credential validation.
Business
Attackers gain unauthenticated access to the management interface without requiring valid credentials.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I query the alternate path to retrieve stored credential data cached or persisted within the application.
Business
Sensitive credentials stored in Endpoint Manager become accessible to unauthorized parties.
3
Lateral reach — past segmentation narrative 3
Attacker
I exfiltrate the leaked credentials for use in lateral movement or further compromise of managed endpoints.
Business
Compromised credentials enable attackers to access endpoints and systems managed by EPM, expanding the breach scope across the organization's infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05