Ivanti Patches Two More Connect Secure Zero-Days Chained for Root Access

Ivanti patched two more Connect Secure zero-days an attacker chained with an auth bypass to root fully patched VPN gateways.

@sharedot

Ivanti Patches Two More Connect Secure Zero-Days Chained for Root Access

By @sharedot · · 7 pages

  • Cybersecurity
  • Ivanti
  • Connect Secure
  • Zero Day
  • Vpn

Ivanti patched two more Connect Secure zero-days an attacker chained with an auth bypass to root fully patched VPN gateways.

What happened: the last two holes in a three-bug chain are closed

Ivanti released security updates on Thursday for two more Connect Secure (ICS) remote access gateway flaws, tracked as CVE-2026-111357 and CVE-2026-118527, extending its October 13 advisory for the authentication bypass CVE-2026-104935.

Attackers had chained all three flaws since at least the start of October, well before fixes existed for the full chain.

CVE-2026-111357 is a high-severity privilege escalation flaw Ivanti rates 8.8 on the CVSS scale, stemming from a lack of authentication for a critical function, while CVE-2026-118527 lets authenticated attackers upload files of their choosing to a known disk location and scores 4.3.

The new fixes ship in versions 25.1.1.3 and 22.8R2.6, meaning organizations that installed last month's CVE-2026-104935 patches (versions 25.1.1.2 and 22.8R2.5) need to upgrade again. According to Ivanti, the attacks had hit a limited number of customers by the time they were disclosed.

Why it's surprising: a fileless attacker that stayed invisible

The exploitation technique stood out to the firm that found it. Volexity, which uncovered the in-the-wild attacks while investigating an incident at one of its customers, reported that the threat actor it tracks as UTA0576 deployed no malware or web shell.

Instead, it re-exploited the device for every command it ran and tampered with logs to cover its tracks, evading Ivanti's own Integrity Checker Tool.

By chaining the authentication bypass with the privilege escalation and file upload bugs, the hackers obtained unauthenticated code execution with root privileges on an ICS appliance that was fully patched at the time.

Volexity assesses with low confidence that UTA0576 is criminally motivated rather than an espionage group, and it had never documented the actor before. Defused separately reported attacks against its decoys starting October 1, before the vulnerability was public.

The evidence: what the intruders did inside victim networks

Volexity saw the first signs of exploitation on October 3, while BleepingComputer reports that threat intelligence firm Defused spotted the first signs of active CVE-2026-104935 exploitation starting October 1.

CISA added CVE-2026-104935 to its Known Exploited Vulnerabilities catalog on October 13, and on Friday added the two newly patched flaws, giving federal agencies until November 2 to address CVE-2026-111357 and until November 13 for CVE-2026-118527.

Ivanti explained in an updated advisory that its CVE-2026-104935 fix was already in QA when exploitation was discovered, and it chose not to delay shipping the fix that closed the primary exploitation path.

The stakes: thousands of gateways still exposed

BleepingComputer reports that internet threat watchdog Shadowserver now tracks over 5,000 internet-exposed Connect Secure instances, though there is no information on how many have already been secured against ongoing attacks.

Because the attacks ran from early October, patching now may not be enough — a device that was online and unpatched may already be compromised, and Ivanti says dependable indicators of compromise are not available.

The affected organizations are businesses that run Connect Secure themselves, from clinics and law firms to schools and local governments, and a successful break-in hands intruders the keys to the internal network.

Ivanti's track record raises the pressure further: BleepingComputer counts 38 Ivanti vulnerabilities CISA has flagged as actively exploited since November 2021, including 12 also abused in ransomware attacks.

What comes next: patch, then hunt for signs of intrusion

Admins running Connect Secure should check the exact version in the admin panel and upgrade to 25.1.1.3, 22.8R2.6, or later.

Beyond patching, organizations should assume possible compromise for any gateway that was online and unpatched since early October, reset passwords for every account that used the gateway — especially administrators and service accounts — and review sign-in logs on domain controllers and email for odd activity dating back to October 1.

Rotating BitLocker recovery keys is advised if administrators stored them where the gateway could reach them. Defenders are cautioned not to rely on Ivanti's Integrity Checker Tool alone, given the log-tampering behavior Volexity documented, though Volexity has published some indicators on GitHub.

BleepingComputer notes threat actors frequently target Ivanti flaws in zero-day attacks as a quick way into enterprise networks.

Sources

  1. bleepingcomputer.com › Ivanti patches two more Connect Secure zero-days chained in attacks
  2. securityweek.com › Ivanti Patches Two More Zero-Days Exploited in Connect Secure Attack Chain
  3. 2-spyware.com › Ivanti Connect Secure zero-days chained for root access

More on Cybersecurity