Ivanti Connect Secure Zero-Day Chain: Two Flaws Added to CISA KEV
Dr. Abeer Alshammari · Published 11/9/2026
Vulnerability Intelligence
- CVE
- CVE-2026-111357, CVE-2026-118527, CVE-2026-104935
- Affected product
- Ivanti Connect Secure
- Exploit status
- Actively exploited
- CISA KEV listed
- Yes
- Patch status
- Fixed by Ivanti updates; confirm exact builds in the Ivanti advisory
CyberAbeer's own prioritization guidance, based on severity, known exploitation, and exposure -- not an official vendor or CISA rating.
Sources last checked 11/9/2026
Bottom line: Ivanti Connect Secure appliances were hit by a zero-day chain, and CISA has added two of the flaws to its Known Exploited Vulnerabilities catalog. Patching is necessary but not sufficient: teams must also check for compromise.
What happened
CISA added CVE-2026-111357 and CVE-2026-118527, both affecting Ivanti Connect Secure, to the KEV catalog on 2 November 2026. Volexity discovered the attacks and reported them to Ivanti, and attributes the activity to a cluster it tracks as UTA0576. According to coverage of the advisories, the two flaws were chained with a third bug, CVE-2026-104935, which is described as an authentication bypass leading to remote code execution. Whether that third CVE is in the KEV catalog was not stated in the coverage I could open.
Why it matters
SSL VPN gateways sit on the network edge and hold the keys to internal systems. Volexity reports that the activity evades Ivanti's Integrity Checker Tool, so a clean scan does not prove a clean appliance. Rapid7 reports that the attackers stole credentials and queried Active Directory for Windows LAPS passwords and BitLocker recovery keys. Volexity assesses with high confidence that this was preparation for lateral movement.
Who is affected
Organisations running Ivanti Connect Secure, including government, finance, energy and telecom operators across the region that rely on it for remote access. Affected and fixed version numbers were not stated in the coverage I reviewed, so check Ivanti's own advisory for exact builds.
Technical impact
CVE-2026-111357 is described as a missing authentication for a critical function that allows local privilege escalation. CVE-2026-118527 is described as a predictable identifier weakness that enables authenticated remote file upload. Chained with the authentication bypass, the sequence gives an attacker a path from the internet to code execution and credential theft. A CVSS score was not stated in the sources I opened, so none is given here.
Governance impact
This is a third-party and edge-asset risk that belongs on the risk register. CISA set federal remediation deadlines of 2 November 2026 for CVE-2026-111357 (with forensic triage required) and 13 November 2026 for CVE-2026-118527. Regulated entities should treat those dates as a sensible benchmark and be ready to evidence patching, investigation and credential rotation to auditors.
What security teams should do
Apply Ivanti's updates now. Then investigate for compromise even if the Integrity Checker is clean. Preserve memory and logs before rebooting or resetting the appliance where feasible. Hunt using Ivanti's guidance and the indicators and YARA rules published by Volexity. If compromise is suspected, follow Ivanti's recovery steps and rotate potentially exposed credentials, including LAPS passwords and BitLocker recovery keys.
What executives should know
Patching alone does not close this incident. Ask your CISO three questions: are our Ivanti gateways updated, have we checked them for signs of compromise, and have exposed credentials been rotated. A yes to the first only is not enough.
Sources: CISA Known Exploited Vulnerabilities catalog entries as reported by Help Net Security (2 November 2026), citing Volexity and Rapid7. The primary Ivanti advisory was not opened in this review, so confirm version details there.