Ivanti Connect Secure VPN: Three Chained Flaws Exploited, Fixes Now Complete (CVE-2026-104935)
Attackers chained three Ivanti Connect Secure flaws to break into VPN appliances at a limited number of customers. Fixes for all three are out. Update to 25.1.1.3 or 22.8R2.6, or run 25.1.3.0 or later, and run Ivanti's Integrity Checker Tool to look for signs of compromise.
Updates
- : Ivanti released 25.1.1.3 and 22.8R2.6, fixing two more flaws (CVE-2026-111357 and CVE-2026-118527) that attackers chained with the original one. CISA added both to its exploited list the same day.
What happened
On 13 October 2026, Ivanti disclosed CVE-2026-104935, an authentication bypass in Ivanti Connect Secure (ICS), its VPN appliance. It lets a remote attacker run commands on the appliance without logging in. CISA added it to its Known Exploited Vulnerabilities catalog the same day.
Ivanti later confirmed that attackers had chained it with two more flaws: CVE-2026-111357, which lets a logged-in attacker escalate to full control of the appliance, and CVE-2026-118527, which lets an authenticated attacker upload files to a predictable location. Ivanti released fixes for those two on 29 October, and CISA added them to the catalog on 30 October.
A VPN appliance is the front door to the office network. Taking it over gives an attacker a trusted position to move further in, often without setting off alarms.
Who is affected
Per Ivanti's advisory:
- CVE-2026-104935: Connect Secure 25.1.1.1 and earlier, 25.1.2.2 and earlier, and 22.8R2.4 and earlier. Version 22.7R2.14 and earlier are not affected.
- CVE-2026-111357 and CVE-2026-118527: Connect Secure 25.1.1.2 and earlier, and 22.8R2.5 and earlier.
- Versions 25.1.3.0 and later (released July 2026, on ISA4500, ISA6500 or ISA8500) do not contain the vulnerability.
Ivanti also reminds customers that the 22.7 and 22.8 lines reach end of life on 31 January 2027, so anyone still on them needs a plan to move to 25.1.
Is it being exploited?
Yes. Ivanti says it is aware of exploitation affecting a limited number of customers when the three flaws are chained. All three are on CISA's Known Exploited Vulnerabilities list. CISA has not said whether ransomware groups are using them.
When to get outside help
Ivanti says there are limited indicators of compromise for this attack, so a clean result from a quick check isn't a guarantee. If your appliance was running an affected version while the attacks were happening, an incident response firm can review it and the network behind it. Planning the move off 22.7 or 22.8 before January is also a good job for a managed security provider or consultant, because 25.1.3.0 needs new hardware or newly built virtual appliances.
What to do
- Update. Ivanti's fixed versions that resolve all three flaws are 25.1.1.3 (for 25.1.1.x on ISA6000 or ISA8000) and 22.8R2.6 (for the 22.8 line). Versions 25.1.3.0 and later are not affected. Ivanti recommends that 22.8 customers move to 25.1.1.3 or later.
- Check for compromise. Run Ivanti's Integrity Checker Tool regularly, as Ivanti recommends. Review the indicators of compromise in the Volexity research linked from Ivanti's advisory.
- If you suspect a breach, follow the recovery steps in Ivanti's advisory rather than just patching.
- Plan your upgrade. Moving off 22.7 and 22.8 needs to be done before they reach end of life on 31 January 2027. Moving to 25.1.3.0 needs ISA4500, ISA6500 or ISA8500 hardware, or virtual devices built from the 25.1.3.0 template.
Related guides
Sources
Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.
