Steve Miller's Blog

A digital workshop for systems-minded tech commentary.

Attackers Chained Three Ivanti Connect Secure Flaws Into Unauthenticated Root: Why Your Remote-Access Appliance Needs an Exit Plan, Not Another Hotfix

Three network security engineers discuss patching beside server racks in a data center aisle.

Written by

in

The VPN appliance was supposed to be the lock on the front door. After years of emergency advisories, the more useful question isn’t whether this latest patch works. It’s how many more times you’re willing to rebuild trust in the same box. The newest Ivanti Connect Secure vulnerability root access chain makes that question hard to dodge: three flaws, used together in the wild, ending in unauthenticated code execution as root on a device that was fully patched at the time.

What Volexity Found

Volexity published its analysis on October 13, 2026. In the first week of October, it found a previously unknown threat actor it tracks as UTA0576 “abusing a zero-day exploit chain to compromise a fully patched (at the time, version 22.8R2.4) Ivanti Connect Secure (ICS) VPN appliance.” In Volexity’s words, the chain “combined an authentication bypass, a remote code execution (RCE), and a privilege escalation vulnerability to achieve unauthenticated root-level code execution.”

The mechanics, per Volexity:

  • Authentication bypass: a request to the public login script welcome.cgi names a different, protected script in an X-DSCGI-PATH header. The URL decides whether the request is allowed. The header decides where it goes.
  • Code execution: the wu.cgi upload handler writes a file to a predictable path before checking whether it is a valid ZIP. The attacker races to execute it before it is deleted.
  • Root: the root-level dsinvoked service trusts program paths stored in the DSCache configuration store. After patching a library in memory and altering a cached entry, the attacker gets dsinvoked to run a script as root. The exploit then restores the original state and trims log entries.

Volexity says UTA0576 used the access to extract credentials stored on the appliance, dump limited Active Directory metadata, search Active Directory for LAPS passwords and BitLocker recovery keys, capture LDAP traffic, and run password spraying. It found no backdoor or web shell. The actor re-ran the whole chain for every command. Volexity assesses, with low confidence, that the motivation is criminal rather than espionage.

What Ivanti’s Advisory Says About the Ivanti Connect Secure Vulnerability Root Access Chain

Ivanti’s security advisory now covers three CVEs:

  • CVE-2026-104935, 8.6 (High): authentication bypass by spoofing that “allows a remote unauthenticated attacker to execute arbitrary commands.” Volexity notes Ivanti tracks both the bypass and the RCE portion under this CVE.
  • CVE-2026-118527, 4.3 (Medium): use of predictable filenames that lets a remote authenticated attacker upload attacker-controlled content to a known location on disk. Ivanti doesn’t spell out which step this covers; my inference is that it corresponds to the predictable upload path in wu.cgi that Volexity describes.
  • CVE-2026-111357, 8.8 (High): missing authentication for a critical function that lets a local authenticated attacker escalate privileges.

Ivanti says, “We are aware of exploitation in the wild affecting a limited number of customers at the time of disclosure when CVE-2026-104935, CVE-2026-111357 and CVE-2026-118527 are chained.” So this is confirmed exploitation, not a proof of concept. That said, the public forensic detail comes from Volexity’s investigation of a single customer’s appliance.

Versions and the Two-Stage Fix

The fix arrived in two pieces. According to Ivanti’s advisory, CVE-2026-104935 affects 25.1.1.1 and prior, 25.1.2.2 and prior, and 22.8R2.4 and prior. It is resolved in 25.1.1.2, 25.1.3.0 or 25.1.3.1, and 22.8R2.5. Volexity says those patches were released October 13, 2026. The other two flaws affect 25.1.1.2 and prior and 22.8R2.5 and prior, and are resolved in 25.1.1.3 and 22.8R2.6. Volexity’s update says Ivanti published the privilege escalation fix on October 29.

That sequencing matters. If you patched on October 13 and stopped, Ivanti’s table says you are not on a version that resolves the full chain. Ivanti recommends 22.8 customers move to 25.1.1.3 or later. It notes that 22.8 is meant as “a temporary bridge” and reaches end of life on January 31, 2027. For those who can’t move yet, 22.8R2.6 “resolves all vulnerabilities in this disclosure.”

CISA’s alert says it added CVE-2026-104935 to the Known Exploited Vulnerabilities catalog on October 13, and the other two on October 30. CISA is “aware of cyber threat actors exploiting these vulnerabilities” to conduct credential theft and data exfiltration.

Why the Integrity Checker Isn’t Enough

CISA and Volexity both warn that Ivanti’s Integrity Checker Tool may not detect this. Volexity explains that “because this exploit chain patches library code in memory only and restores configuration store data, the tool does not detect any modifications.” CISA says organizations “will need to conduct network and memory forensics to identify evidence of exploitation.”

If you suspect compromise, CISA points to Ivanti’s recovery steps. Back up the configuration, factory reset (or rebuild virtual instances) and upgrade, restore the configuration, then reset passwords for all accounts, including domain, administrator, and local accounts. Revoke and reissue stored certificates, and reset stored API keys and license server credentials.

My Take: Patch Now, Then Plan the Exit

These are my recommendations, not Ivanti or CISA guidance.

  1. Confirm you are on 25.1.1.3, 22.8R2.6, or later. The October 13 release alone does not cover the full chain.
  2. Hunt using Volexity’s indicators. Look for heavy request volume to welcome.cgi with mismatched X-DSCGI-PATH headers, and check /tmp/. Don’t treat a clean Integrity Checker result as proof.
  3. Rotate what passed through the box. Volexity saw LDAP service account abuse and LAPS and BitLocker key searches. If you can’t rule out exposure, rotate the appliance’s AD service account and review those secrets.
  4. Write an exit plan. 22.8 has an end-of-life date. Use it as a forcing function to evaluate whether an internet-facing VPN appliance is still the right model, or whether identity-aware access with less exposed surface fits better.
  5. Put edge devices in your memory-forensics plan. This attacker built for appliances that don’t log well. Your incident response playbook should assume the same.

A hypothetical to test your readiness: your appliance was patched October 13, and your Integrity Checker is clean. Can you prove, with network or memory evidence, that nobody ran commands as root on it in the following two weeks? If not, assume the credentials it held are suspect.

The Bottom Line

Ivanti, Volexity, and CISA all confirm in-the-wild exploitation of a three-CVE chain that Volexity says reaches unauthenticated root. Patch to the full fix, hunt beyond the Integrity Checker, rotate what the appliance touched, and decide how many more of these cycles you’re willing to run.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *