CriticalVulnerabilityPatch available

Ivanti Connect Secure zero-day chain (CVE-2026-104935, CVE-2026-111357, CVE-2026-118527) gave root on fully patched VPNs

Three chained Ivanti Connect Secure flaws give unauthenticated root and evade the Integrity Checker. Upgrade to 25.1.3.1, 25.1.1.3 or 22.8R2.6.

Published
Updated
Fixed in
Ivanti Connect Secure 25.1.3.1, 25.1.1.3, 22.8R2.6 (full chain); 25.1.3.0 for CVE-2026-104935 only
Exploitation
Yes. Defused saw signs from 1 October 2026 and Volexity from 3 October (actor UTA0576); CVE-2026-104935 in CISA KEV since 13 October, the other two since 30 October

Live scores

CVE-2026-104935
EPSS
0.889
very likely to be attacked soon
VEDAS
0.984
strong exploit evidence
On CISA KEV
Yes, since 2026-10-13
Detection rule
No public rule yet
EPSS (chance of attack)
100.1CVE-2026-104935 EPSS over time2026-102026-11-11
VEDAS (exploit evidence)
100.5CVE-2026-104935 VEDAS over time2026-102026-11-11

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

Live scores

CVE-2026-111357
EPSS
0.005
low predicted chance of attack
VEDAS
0.516
likely exploited
On CISA KEV
Yes, since 2026-10-30
Detection rule
Out of scope (local)
EPSS (chance of attack)
100.1Added to CISA KEV 2026-10-30CVE-2026-111357 EPSS over time2026-102026-11-11
VEDAS (exploit evidence)
100.5Added to CISA KEV 2026-10-30CVE-2026-111357 VEDAS over time2026-102026-11-11

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

Live scores

CVE-2026-118527
EPSS
0.008
low predicted chance of attack
VEDAS
0.511
likely exploited
On CISA KEV
Yes, since 2026-10-30
Detection rule
No public rule yet

What happened

Volexity found a previously unknown actor, UTA0576, exploiting Ivanti Connect Secure (ICS) from 3 October 2026. The victim ran ICS 22.8R2.4, which was fully patched at the time (Volexity). Defused said it first saw signs of exploitation on 1 October (BleepingComputer).

The chain has three steps (Volexity):

  1. Authentication bypass. The public endpoint /dana-na/auth/url_default/welcome.cgi routes a request to a protected CGI script named in an X-DSCGI-PATH header, while the access check looks only at the URL.
  2. File write and code execution. The upload handler wu.cgi writes a file to disk before it checks the file is a valid ZIP. The attacker races parallel requests to run the file before it is deleted.
  3. Root. The exploit patches libdsplibs.so in memory, changes a DSCache maintenance task, and gets the root dsinvoked service to run its script. It then restores both.

Ivanti’s CVE record says CVE-2026-104935 is an authentication bypass that lets a remote unauthenticated attacker run arbitrary commands. It affects ICS before 25.1.3.0; 22.7R2.14 and earlier are not affected (CVE record). CVE-2026-111357 is the dsinvoked and DSCache privilege escalation to root (CVE record). CVE-2026-118527 is a predictable-identifier flaw that lets an authenticated attacker upload attacker-controlled files to a known location on disk (CISA KEV).

The fix came in two parts. Ivanti disclosed CVE-2026-104935 first, on 13 October, because its fix was already in QA, and added the other CVEs once they were found (Security Affairs). Volexity updated its post on 29 October when Ivanti patched the privilege escalation. CISA added CVE-2026-104935 to KEV on 13 October (due 16 October), and CVE-2026-111357 and CVE-2026-118527 on 30 October (due 2 and 13 November) (CISA KEV).

What the attacker did. UTA0576 installed no web shell or backdoor. It re-ran the whole chain for every command. It went after Active Directory: LDAP queries for LAPS passwords, BitLocker recovery keys and password attributes, Kerberoasting, password spraying, and packet capture of LDAP traffic on the appliance. It also tampered with logs (Volexity).

Shadowserver tracked over 5,500 exposed ICS instances when the bug was disclosed (BleepingComputer).

Am I affected?

CISA lists ICS 25.1.1.2 and earlier, 25.1.2.2 and earlier, and 22.8R2.5 and earlier as affected (CISA). The Canadian Centre for Cyber Security lists the fixed builds as 25.1.1.3, 25.1.3.1 and 22.8R2.6 (Cyber Centre), which matches Security Affairs’ reading of Ivanti’s update. Ivanti’s own advisory page did not load for us; confirm the build for your branch there before you upgrade.

Check the version shown in the ICS admin console against those numbers. A box upgraded to 25.1.3.0 on 13 October is fixed for the authentication bypass but not for the full chain.

Do not rely on the Integrity Checker Tool (ICT). Because the exploit patches libraries in memory and restores the configuration, Volexity found the ICT “does not detect any modifications” (Volexity). CISA says network and memory forensics are needed (CISA).

Indicators from Volexity:

  • Source IP 108.165.147[.]64.
  • High volumes of requests to /dana-na/auth/url_default/welcome.cgi, and requests whose X-DSCGI-PATH header does not match the URL. Seen values: X-DSCGI-PATH: /home/webserver/htdocs/dana/fb/smb/wu.cgi and X-DSCGI-PATH: /home/runtime/tmp/<MD5 of filename>.
  • Files on the appliance (for a forensic image or Ivanti support): /tmp/ml.py, /tmp/rq5.py, /tmp/mk.py, /tmp/rr.py, /tmp/sp_run.py, /tmp/sp_out.txt, /tmp/spray_hits.json, /tmp/pu.txt, /data/.icscap/h.py, /data/.icscap/cap*, /home/runtime/tmp/ics-root-run-inband-*.pl and /home/runtime/tmp/ics-root-result-inband-*.
  • A renamed tcpdump running as /data/.icscap/dsstatmond.
  • Gaps or edits in /home/runtime/dlogs/debuglog and /var/log/audit/audit.log.

Volexity publishes further indicators in its threat-intel repository.

What to do now

  1. Upgrade to 25.1.3.1, 25.1.1.3 or 22.8R2.6 or later, after checking the exact build for your branch in Ivanti’s advisory. CISA points to Ivanti’s 25.x upgrade and compatibility guide for hardware and virtual appliances, and notes ICS 22.8 reaches end of life on 31 January 2027 (CISA).
  2. If compromise is possible, follow CISA’s recovery steps: back up the configuration, factory reset (or rebuild a virtual instance), upgrade, then restore the configuration (CISA).
  3. Reset what the appliance could reach. CISA says to reset passwords for all domain, administrator and local accounts, revoke and reissue stored certificates, and reset stored API keys and license server credentials. Given what UTA0576 targeted, also rotate LAPS-managed local admin passwords and BitLocker recovery keys that are readable from AD, and service account passwords that could be Kerberoasted.
  4. Search your web and proxy logs in front of the appliance for welcome.cgi bursts and X-DSCGI-PATH headers from 1 October onward, and block 108.165.147[.]64.
  5. Look inside your network, not just on the box. Volexity says devices showing lateral movement from the VPN appliance “should be forensically investigated.” Check domain controllers for LDAP queries and Kerberos service ticket requests sourced from the ICS internal IP.

Update, 8 November 2026

  • Ivanti rates CVE-2026-111357 at 8.8 (CVSSv3.1) and describes it as a missing authentication for a critical function flaw that allows a local authenticated attacker to escalate privileges. (rapid7.com)
  • Rapid7 says the CVE record and Rapid7’s vulnerability database rate CVE-2026-111357 at 7.0, using high attack complexity and unchanged scope, while Ivanti assesses low attack complexity and changed scope. (rapid7.com)
  • Ivanti rates CVE-2026-118527 at 4.3 (Medium, CVSSv3.0) and CVE-2026-104935 at 8.6 (High, CVSSv3.0). (rapid7.com)
  • Ivanti’s updated advisory classifies CVE-2026-104935 as CWE-290, CVE-2026-111357 as CWE-306, CWE-862 and CWE-345, and CVE-2026-118527 as CWE-340. (rapid7.com)
  • According to Ivanti, attacks chaining the three flaws had hit a limited number of customers by the time they were disclosed. (securityweek.com)
  • SecurityWeek says versions 25.1.1.2 and 22.8R2.5 were the releases that patched CVE-2026-104935 on those branches, so organizations that installed them in response to the initial advisory will need to upgrade again. (securityweek.com)
  • Ivanti says it discovered a portion of the vulnerability through its product security program and patched it in the July release 25.1.3.0, and was working to backport the fix to other supported versions when exploitation occurred. (thehackernews.com)
  • Ivanti says the latest release addresses all vulnerabilities which were chained and exploited in the wild. (thehackernews.com)
  • BleepingComputer reported on 2 November 2026 that Shadowserver now tracks over 5,000 Internet-exposed ICS instances, with no information on how many have been secured. (bleepingcomputer.com)
  • Volexity says the threat actor’s ultimate objectives could not be determined because the operation was detected and disrupted. (helpnetsecurity.com)
  • Volexity assesses with high confidence that UTA0576’s actions signaled preparation for lateral movement and a broader compromise of the victim network. (helpnetsecurity.com)
  • Help Net Security says CISA ordered US federal civilian agencies to engage in forensic triage and investigate for possible compromise in addition to addressing CVE-2026-111357. (helpnetsecurity.com)
  • Rapid7 advises preserving memory and logs before rebooting or resetting where feasible, says a clean Integrity Checker Tool result does not rule out compromise, and has provided threat hunting guidance. (helpnetsecurity.com)
  • Help Net Security says Volexity has shared YARA rules for this campaign alongside its indicators of compromise. (helpnetsecurity.com)
  • BleepingComputer says CVE-2026-104935 affects ICS versions 22.8R2.4 and earlier, 25.1.2.2 and earlier, and 25.1.1.1 and earlier. (bleepingcomputer.com)
  • BleepingComputer says CVE-2026-104935 can be exploited by remote attackers without privileges in low complexity attacks that require no user interaction. (bleepingcomputer.com)

Update, 9 November 2026

  • Ivanti said at disclosure that it was working directly with the organizations hit by limited exploitation, and told customers to upgrade to the fixed version as soon as possible and run the Integrity Checker Tool regularly. (bleepingcomputer.com)
  • BleepingComputer says CISA has flagged 36 vulnerabilities across various Ivanti products as actively exploited in the wild since November 2021, 12 of which ransomware gangs have also abused. (bleepingcomputer.com)

Sources