CVE-2026-111357: Ivanti Connect Secure Missing Authentication for Critical Function
Ivanti Connect Secure · listed in the CISA catalog of actively exploited vulnerabilities since 2026-10-30.
- CVSS v3.1 (CVE record)
- 7.0
- high
- EPSS (exploit probability, 30 days)
- 0.8%
- higher than 57.6% of all CVEs
- Added to CISA KEV
- 2026-10-30
- US federal due date 2026-11-02
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2026-111357 explained
CVE-2026-111357 is a privilege escalation flaw in Ivanti Connect Secure 22.8R2.4. The dsinvoked broker trusts DSCache configuration data in an unsafe way, which can let a local user gain root. CISA lists it as known exploited, and the description states it was exploited in the wild in October 2026.
Impact
An attacker who already has low-privileged local access can escalate to root on the appliance. No user interaction is needed, but attack complexity is high. CISA rates the technical impact as total, meaning full control of the device. CISA does not rate it as automatable. Root access affects confidentiality, integrity and availability of the gateway. Known ransomware use is listed as unknown.
Who is affected
The CVE record lists Ivanti Connect Secure 22.8R2.4 as affected. The record names no fixed version. This does not mean that no fix exists. Check Ivanti's advisory for patched releases and mitigations. The version data comes from the CVE record published by its CNA (mitre).
Written with AI from the data on this page and checked against it automatically.
Official description
Ivanti Connect Secure 22.8R2.4 mishandles the manner in which the dsinvoked broker trusts DSCache configuration data, leading to privilege escalation to root, as exploited in the wild in October 2026.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
- hub.ivanti.com/s/article/Security-Advisory-Ivanti-Connect…
- cisa.gov/news-events/alerts/2026/10/13/cisa-urges-patchin…
- BOD 26-04: cisa.gov/news-events/directives/bod-26-04-prioritizing-se…
- Forensics Triage Requirements: cisa.gov/news-events/directives/bod-26-04-implementation-…
- nvd.nist.gov/vuln/detail/CVE-2026-111357
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Ivanti Connect SecureAffectedFixed in
- 22.8R2.4
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Ivanti Connect Secure |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: hub.ivanti.com/s/article/Security-Advisory-Ivanti-Connect…
- CISA's deadline for US federal agencies: 2026-11-02 (passed) – a useful benchmark for everyone else, too.
What to do
- Read Ivanti's advisory for CVE-2026-111357 and apply the fixed release or mitigations it provides.
- Follow CISA's required action, including BOD 26-04 guidance and the Forensics Triage Requirements.
- Check appliances for signs of compromise, such as unexpected root activity or configuration changes.
- Restrict local and administrative access to the appliance to trusted users only.
- Evaluate each appliance's internet exposure and keep management interfaces off the internet.
The CVE record names no fixed version. Follow Ivanti's advisory for patches or mitigations. CISA requires applying the vendor's mitigations under BOD 26-04 and its Forensics Triage Requirements. If mitigations are unavailable, CISA directs discontinuing use of the product. Meanwhile, limit access to the appliance and check it for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-829 Inclusion of Functionality from Untrusted Control Sphere
Questions about CVE-2026-111357
- Is CVE-2026-111357 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-10-30. The description says it was exploited in the wild in October 2026. The US federal due date is 2026-11-02.
- Can a remote attacker exploit this directly?
- The CVSS attack vector is local and requires low privileges. An attacker needs existing access to the appliance. They can then escalate to root.
- Which version should I upgrade to?
- The CVE record names no fixed version. Consult Ivanti's advisory for the fixed release or mitigations, and follow CISA's required action.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.