Ivanti Connect Secure CVE-2026-104935: Which Version Fixes the Chain?

Attackers chained three Ivanti Connect Secure flaws to run commands on the VPN appliance as root without a password. The October 13 fix closed only the first one.

Find your fixed version
By CalMax Systems Security Research · Last updated: November 16, 2026

Which version fixes the Ivanti Connect Secure chain?

Upgrade Ivanti Connect Secure to 25.1.1.3 or 22.8R2.6, released October 29, 2026, or run 25.1.3.0 or later. The October 13 releases, 25.1.1.2 and 22.8R2.5, fix only CVE-2026-104935. Attackers chained it with CVE-2026-118527 and CVE-2026-111357, which those builds still contain. If your appliance was exposed, check it for compromise too.

All three flaws are in CISA’s Known Exploited Vulnerabilities catalog: CVE-2026-104935 since October 13, 2026, and the other two since October 30, 2026. Versions 22.7.X and lower are not affected.

Affected and Fixed Ivanti Connect Secure Versions

From Ivanti’s security advisory for CVE-2026-104935 (article 000109571, created October 13, 2026, updated October 29, 2026).

You run CVE-2026-104935 CVE-2026-111357 and CVE-2026-118527 Install
25.1.1.x
ISA6000, ISA8000
25.1.1.1 and prior affected; fixed in 25.1.1.2 25.1.1.2 and prior affected; fixed in 25.1.1.3 25.1.1.3 or later
25.1.2.x 25.1.2.2 and prior affected; fixed in 25.1.3.0 or 25.1.3.1 Not listed in Ivanti’s table for these two CVEs 25.1.3.0 or later (needs the new platform), or 25.1.1.3 on ISA6000/ISA8000
25.1.3.x
ISA4500, ISA6500, ISA8500
Not affected (25.1.3.0 shipped a fix in July 2026) Not listed in Ivanti’s table for these two CVEs Stay current on 25.1.3.x
22.8 22.8R2.4 and prior affected; fixed in 22.8R2.5 22.8R2.5 and prior affected; fixed in 22.8R2.6 25.1.1.3 (Ivanti’s recommendation), or 22.8R2.6 if you can’t move yet
22.7.X and lower Not affected (Ivanti: 22.7R2.14 and prior) Not listed in Ivanti’s table Plan the move to 25.1: 22.7 reaches end of life on January 31, 2027
Upgraded on October 13? Upgrade again. 25.1.1.2 and 22.8R2.5 fix CVE-2026-104935 but are listed as affected by CVE-2026-111357 and CVE-2026-118527. Ivanti says 25.1.1.3 and 22.8R2.6 resolve all vulnerabilities in the disclosure.
22.8 is a temporary bridge. Ivanti says the 22.8 line exists only to move customers from 22.7 to 25.1, and that 22.8 reaches end of life on January 31, 2027. CISA points to the same date. Moving to 25.1.3.0 needs ISA4500, ISA6500 or ISA8500 hardware, or a new virtual or cloud device built from the 25.1.3.0 template.

Ivanti’s advisory lists only Ivanti Connect Secure. It does not mention Ivanti Policy Secure, ZTA gateways or Neurons for Secure Access.

The Three Flaws in the Chain

Ivanti rates two of them high and one medium. Each needs the others to reach root.

CVE Flaw (Ivanti’s wording) Who can use it CVSS (Ivanti) In CISA KEV
CVE-2026-104935 Authentication bypass by spoofing (CWE-290) Remote, unauthenticated; executes arbitrary commands 8.6 High Added October 13, 2026; federal due date October 16
CVE-2026-118527 Use of predictable filenames (CWE-340) Remote, authenticated; uploads attacker-controlled files to a known location on disk 4.3 Medium Added October 30, 2026; due November 13
CVE-2026-111357 Missing authentication for a critical function (CISA KEV name; MITRE’s record lists CWE-829) Authenticated; escalates to root 8.8 High Added October 30, 2026; due November 2
Two scores for CVE-2026-111357. Ivanti rates it 8.8. The CVE record was published by MITRE on October 15, before Ivanti added it to its advisory, and carries a 7.0 score that lists only 22.8R2.4 as affected. Use Ivanti’s advisory for versions.

How the Attack Worked

From Volexity’s October 13, 2026 report. Volexity tracks the attacker as UTA0576 and first saw exploitation on October 3, 2026.

1. Reach a script that shouldn’t be reachable

A request to /dana-na/auth/url_default/welcome.cgi carries an X-DSCGI-PATH header that routes it to a different script, wu.cgi, without logging in. This is the authentication bypass, CVE-2026-104935.

2. Win a race with an upload

wu.cgi writes the uploaded file to disk before it checks it, at a predictable location. The attacker races to run the file before it is removed. Volexity counts this race as part of the chain; Ivanti’s CVE-2026-118527 covers the predictable filenames.

3. Become root

The attacker patches a library in memory so a DSCache maintenance task makes the root dsinvoked service run their script. This is the privilege escalation, CVE-2026-111357.

Volexity says the attacker left no web shell or backdoor and ran the whole chain again for each command. After getting in, it stole the appliance’s stored credentials, including its LDAP service account, searched Active Directory for LAPS passwords and BitLocker recovery keys, ran password spraying against the domain, captured LDAP traffic, and tampered with logs. Its tools could also Kerberoast, though Volexity did not confirm that was used.

Ivanti says it found part of the flaw through its own security program and fixed it in 25.1.3.0 in July 2026; exploitation began while it was backporting that fix to the other supported versions. According to SecurityWeek, the deception company Defused saw attacks on its decoy systems from October 1. BleepingComputer reports that Shadowserver tracks more than 5,000 internet-exposed instances.

Why the Integrity Checker Tool Missed It

Patching closes the chain. It doesn’t tell you whether someone already used it.

Ivanti’s Integrity Checker Tool (ICT) looks for changes to files on the appliance. Volexity says the ICT did not detect this activity, because the exploit patched code only in memory and restored the configuration it changed, and CISA says network and memory forensics are needed to find it. Ivanti still advises running the ICT regularly and reviewing Volexity’s indicators, so run it, but don’t treat a clean result as proof.

Indicators from Volexity (defanged)

CISA’s steps if you suspect compromise

  1. Back up the appliance configuration.
  2. Factory reset the appliance and upgrade it to a fixed version. Rebuild virtual and cloud instances.
  3. Restore the configuration.
  4. Reset every domain, administrator and local password. Revoke and reissue certificates, and reset API keys and license-server credentials.

The attacker went after Active Directory credentials, so treat the domain as exposed too: review service accounts that could be Kerberoasted and failed-login spikes inside the network, not just on the appliance.

Timeline

Date (2026)Event
JulyIvanti ships 25.1.3.0 with a fix for part of the flaw, found by its own security program
October 1Defused sees attacks on decoy systems (per SecurityWeek)
October 3Volexity sees the first exploitation
October 13Ivanti advisory and fixes (25.1.1.2 and 22.8R2.5); Volexity report; CVE-2026-104935 added to CISA KEV; CISA alert
October 29Ivanti adds CVE-2026-111357 and CVE-2026-118527 to its advisory and releases 25.1.1.3 and 22.8R2.6
October 30Both added to CISA KEV; CISA revises its alert
January 31, 202722.7 and 22.8 reach end of life

Where Password Spraying Fits

This chain needed no password. What came after it was all about passwords.

Once inside, UTA0576 harvested credentials and sprayed passwords against the domain from the compromised appliance. That spraying happens inside your network, so an edge block list doesn’t see it; watch for it in your domain controller logs. The password-spraying guide explains what the pattern looks like.

At the edge, VPN login pages face constant password guessing from known attacker addresses. ThreatListPro covers 5.4M+ IPv4 addresses, from real attacks on live production Palo Alto GlobalProtect VPN portals in the US, and it is checked for new attackers every 6 hours. If one of the supported firewalls sits in front of a VPN appliance, it can drop listed sources before they reach the login page.

What a Block List Can’t Do

It does not patch CVE-2026-104935 or the other two flaws, and it doesn’t detect a compromise. An attacker using an address that isn’t on the list is not affected, and ThreatListPro is IPv4 only. Upgrade first, then check the appliance.

Ivanti Connect Secure CVE-2026-104935 FAQs

Is CVE-2026-104935 being exploited?

Yes. Ivanti says it is aware of exploitation affecting a limited number of customers when CVE-2026-104935, CVE-2026-111357 and CVE-2026-118527 are chained. Volexity first saw the attacks on October 3, 2026. CISA added CVE-2026-104935 to its Known Exploited Vulnerabilities catalog on October 13, 2026, and the other two on October 30, 2026.

Which Ivanti Connect Secure version fixes CVE-2026-104935?

Ivanti lists 25.1.1.2, 25.1.3.0 or 25.1.3.1, and 22.8R2.5 as fixed for CVE-2026-104935 alone. To fix all three chained flaws, install 25.1.1.3 or 22.8R2.6, released October 29, 2026, or run 25.1.3.0 or later. Ivanti recommends 25.1.1.3 for customers on 22.8.

Why isn’t the October 13 update enough?

The October 13 releases, 25.1.1.2 and 22.8R2.5, fix only CVE-2026-104935. Ivanti’s advisory lists both builds as affected by CVE-2026-111357 and CVE-2026-118527, the other two flaws in the chain, which were fixed on October 29 in 25.1.1.3 and 22.8R2.6. If you upgraded on October 13, upgrade again.

Is Ivanti Connect Secure 25.1.3 affected?

Ivanti says 25.1.3.0, released in July 2026 for the ISA4500, ISA6500 and ISA8500 platforms, and later versions do not contain this vulnerability, and its table lists the two later flaws only on 25.1.1.x and 22.8. Builds 25.1.2.2 and earlier are affected by CVE-2026-104935. Moving to 25.1.3.0 needs the new hardware or a new virtual or cloud device built from the 25.1.3.0 template.

Did Ivanti’s Integrity Checker Tool detect these attacks?

No. Volexity says the Integrity Checker Tool did not detect this activity, because the exploit worked in memory and restored what it changed, leaving no lasting change to the files the tool checks, and CISA says network and memory forensics are needed. Ivanti still advises running the Integrity Checker Tool regularly and reviewing Volexity’s indicators.

What should I do if my Ivanti appliance may be compromised?

CISA says to back up the configuration, factory reset the appliance and upgrade it, rebuilding virtual and cloud instances, then restore the configuration. Then reset every domain, administrator and local password, revoke and reissue certificates, and reset API keys and license-server credentials.

Are Ivanti Connect Secure 22.7 versions affected?

No. Ivanti says versions 22.7.X and lower do not contain this vulnerability. Both 22.7 and 22.8 reach end of life on January 31, 2027, and Ivanti says customers should move to the 25.1 line before that date.

Sources

Cut the Password Guessing at Your VPN Edge

ThreatListPro covers 5.4M+ IPv4 addresses and is checked for new attackers every 6 hours. Monthly is $19.99 with a 14-day free trial and no card needed.

Start a 14-day free trial Or test 200 entries first: free, no signup

Firewall Guides

ThreatListPro uses a plain-text feed for firewalls that support external IPv4 address lists.

Palo Alto FortiGate pfSense OPNsense SonicWall Cisco ASA Sophos XG UniFi

Related Resources

More dated alerts, and the credential attacks that follow a VPN compromise.

Security Alerts: VPN, Firewall and Remote Access Attacks Password Spraying on VPNs VPN Brute Force Explained VPN Account Lockout Prevention Block an IP Address at the Firewall Residential Proxy VPN Attacks