Ivanti Connect Secure flaws exploited: what to do now

By the NexusSec team · 4 min read · Published
Short version: On 30 October 2026, CISA added two more Ivanti Connect Secure flaws, CVE-2026-111357 and CVE-2026-118527, to its catalogue of actively exploited vulnerabilities. Attackers chained them with CVE-2026-104935 to take full control of VPN appliances without logging in, including appliances that were fully patched at the time. Ivanti's fixes are in Connect Secure 22.8R2.6 and 25.1.1.3. Upgrade now and check for signs of compromise.

VPN appliances sit on the internet by design, which makes them one of the first things attackers try. This post reflects what was published up to 1 November 2026.

What happened

In early October 2026, the security firm Volexity found a threat actor it tracks as UTA0576 breaking into Ivanti Connect Secure VPN appliances that were fully patched at the time. The attackers chained three flaws to run code as root without logging in:

CISA added the last two to the KEV catalogue on 30 October 2026, which means it has evidence they are being exploited. US federal agencies were given until 2 November and 13 November to fix them.

What the attackers went after

According to reporting on Volexity's findings, once the attackers controlled an appliance they went after Active Directory credentials and other sensitive data, including LAPS passwords and BitLocker recovery keys. A VPN appliance holds the keys to the network behind it, which is why flaws like these matter far beyond the appliance itself.

Which versions fix it

Reports say Ivanti has published no workaround for the two newest flaws, so the upgrade is the fix. Check Ivanti's own advisory for your exact version.

What to do

  1. Find every Ivanti Connect Secure appliance, including old ones nobody uses any more but that are still reachable from the internet.
  2. Upgrade to 22.8R2.6 or 25.1.1.3.
  3. Look for signs of compromise: unexpected administrator accounts, unusual VPN sessions, and connections from the appliance to internal servers. Volexity advises a forensic investigation of any appliance that shows such signs.
  4. If you find signs of compromise, treat credentials that passed through the appliance as exposed: reset affected Active Directory passwords, rotate service-account and LDAP bind passwords, and rotate LAPS passwords and BitLocker recovery keys.
  5. Keep the admin interface off the internet, reachable only from internal management networks.

The bigger pattern

October 2026 brought exploited flaws in several vendors' edge devices, including Cisco's firewalls and the k0t credential campaign against Fortinet and Palo Alto devices. If your VPN is still the main way into your network, see VPN or ZTNA and firewall edge attacks.

Sources

Frequently asked questions

Is Ivanti Connect Secure being exploited?

Yes. CISA added CVE-2026-111357 and CVE-2026-118527 to its Known Exploited Vulnerabilities catalogue on 30 October 2026, and CVE-2026-104935 on 13 October.

Which Ivanti Connect Secure version fixes it?

22.8R2.6 for the 22.8 line and 25.1.1.3 for the 25.1 line. Check Ivanti's advisory for your exact version.

We patched in early October. Are we safe?

Not necessarily. The attacks hit appliances that were fully patched at the time. Upgrade to the fixed versions above and check the appliance for signs of compromise.

What should we do if our appliance was compromised?

Investigate it properly, and treat credentials that passed through it as exposed: reset Active Directory passwords, rotate service and LDAP accounts, and rotate LAPS passwords and BitLocker recovery keys.

Running an internet-facing VPN?

We review what your VPN and firewall expose to the internet, help you patch, and look for signs that someone got in.

Book a free consultation