← All Posts
securityIvantiCVE

Ivanti Connect Secure Zero-Days: Two More Now Exploited

November 5, 2026

Ivanti has fixed the last two flaws in the Connect Secure exploit chain, and CISA added both to its Known Exploited Vulnerabilities catalog on October 30. CVE-2026-111357 is a privilege escalation bug and CVE-2026-118527 is an authenticated file upload, and attackers used them alongside the CVE-2026-104935 authentication bypass to get root on appliances. If you run Connect Secure, update to a fixed build, then check for compromise, because a clean patch doesn't prove you weren't hit.

This follows the first patch from October 13, which our October vulnerability roundup covered while the privilege escalation fix was still pending.

Key Takeaways

  • Fixed builds reported by The Hacker News are 25.1.1.3 and 22.8R2.6, and CISA's KEV catalog now lists both new CVEs.
  • The attackers, tracked by Volexity as UTA0576, used no malware or web shells and re-exploited the appliance for each command.
  • Ivanti's Integrity Checker Tool can miss this activity, per CISA and Volexity, so a clean scan isn't proof of safety.
  • Preserve logs and memory before rebooting, and rotate credentials the appliance could have exposed.

What are the two new Ivanti Connect Secure flaws?

The Hacker News lists the details:

  • CVE-2026-111357 (CVSS 8.8): missing authentication for a critical function. A local, authenticated attacker can escalate privileges.
  • CVE-2026-118527 (CVSS 4.3): predictable identifiers. A remote, authenticated attacker can upload files to a known location on disk.
  • CVE-2026-104935 (CVSS 8.6): the authentication bypass that Ivanti patched on October 13, which was also added to KEV that day.

Reports describe CVE-2026-104935 as covering the authentication bypass and code execution stages, and CVE-2026-111357 as the privilege escalation step. The sources I read don't spell out exactly where the file upload flaw fits in the chain, so I won't guess.

Which Connect Secure versions are fixed?

The Hacker News reports that 25.1.1.2 and earlier is fixed in 25.1.1.3, and 22.8R2.5 and earlier is fixed in 22.8R2.6. The Canadian Cyber Centre's advisory lists vulnerable versions as those prior to 25.1.1.3, 25.1.3.1 and 22.8R2.6, so the 25.1.3 line needs 25.1.3.1.

Check Ivanti's advisory for your exact branch before you upgrade. Sources: Canadian Cyber Centre.

Federal civilian agencies were told to patch CVE-2026-111357 by November 2 and CVE-2026-118527 by November 13. Help Net Security says CISA also told them to run forensic triage for possible compromise.

How did the attackers get root on patched devices?

According to Cybersecurity Dive, Volexity started working with Ivanti on October 5 after spotting odd activity on a customer's fully patched appliance. Volexity traced the activity back to October 3, and Defused says it saw activity as early as October 1.

Volexity tracks the actor as UTA0576, a previously unknown group it suspects is criminal rather than espionage-driven. It chained an authentication bypass, a code execution step and a privilege escalation to get unauthenticated root-level code execution.

The tradecraft is the part worth reading twice. The attackers deployed no malware and no web shells. They re-exploited the device for every command, deleted evidence from Ivanti debug logs and Linux audit logs, and went after Active Directory secrets such as Windows LAPS passwords and BitLocker recovery keys.

Volexity suspects the attackers used large language models, based on how they ran commands and scripts with hardcoded credentials, but The Register notes that's an inference.

How do I check whether my appliance was compromised?

Patch first, then hunt. Help Net Security summarizes the guidance from Volexity and Rapid7:

  • Don't treat a clean Integrity Checker Tool result as an all-clear. CISA warns that commands run in memory, so the tool may not see them.
  • Preserve memory and logs before you reboot or reset the appliance, where feasible.
  • Watch for authentication failures that come from the appliance's internal interface. Volexity's team calls that a telltale sign of a likely compromised device.
  • Review the indicators and YARA rules Volexity has published on GitHub.
  • If you suspect compromise, follow Ivanti's recovery steps and rotate credentials the device could have exposed.

Given what the attackers went after, include Active Directory service accounts, LAPS passwords and BitLocker keys in that rotation if the appliance could reach them. That last step is my reading of the targeting, not an instruction from Ivanti.

How exposed is Connect Secure?

BleepingComputer says Shadowserver tracks over 5,000 internet-exposed Connect Secure instances, and nobody knows how many are patched. It also notes that CISA has flagged 38 Ivanti vulnerabilities since November 2021, 12 of which were used in ransomware attacks.

The Register notes this is the third year in a row Ivanti has dealt with attackers exploiting undisclosed Connect Secure flaws.

Wrapping Up

Upgrade Connect Secure to 25.1.1.3, 25.1.3.1 or 22.8R2.6 or later, depending on your branch, and then assume nothing until you've checked logs for the signs above. If you find them, rotate the Active Directory secrets first.

Sources

Frequently Asked Questions

Which Ivanti Connect Secure versions fix CVE-2026-111357 and CVE-2026-118527?

The Hacker News reports 25.1.1.3 and 22.8R2.6, and the Canadian Cyber Centre lists 25.1.3.1 as the threshold for the 25.1.3 line. Check Ivanti's advisory for your exact branch before upgrading.

Are the new Ivanti Connect Secure flaws exploited?

Yes. CISA added CVE-2026-111357 and CVE-2026-118527 to its Known Exploited Vulnerabilities catalog on October 30, 2026. Volexity saw them chained with CVE-2026-104935 against Connect Secure appliances.

Can Ivanti's Integrity Checker Tool detect this attack?

Not reliably. CISA and Volexity warn that the attackers' commands run in memory, so a clean Integrity Checker result doesn't rule out compromise.

What should I do after patching Ivanti Connect Secure?

Hunt for compromise: preserve memory and logs, review Volexity's published indicators and YARA rules, and look for authentication failures from the appliance's internal interface. If you suspect a breach, follow Ivanti's recovery steps and rotate exposed credentials.

Who is behind the Ivanti Connect Secure attacks?

Volexity tracks the actor as UTA0576, a previously unknown group it suspects is criminally motivated. The operation was disrupted, so the attackers' final goals are unknown.