Security Digest · Oct 13, 2026 · Vulnerability · Network edge

Ivanti Connect Secure CVE-2026-104935 Chain: Patch Again

Exploited Ivanti Connect Secure chain to root: the Oct 29 fix covers two more KEV CVEs, and 22.8R2.5 is vulnerable. Go to 25.1.1.3 or 22.8R2.6 and do forensics.

Our verdict

Act now

Upgrade Connect Secure again, even if you patched on October 13, because the root escalation fixed on October 29 is exploited and in KEV; then investigate with memory and network forensics, since the Integrity Checker missed this chain.

Who must act: Every organization running Ivanti Connect Secure 22.8 or 25.1.1/25.1.2 builds, including those that installed 22.8R2.5 or 25.1.1.2 for the October 13 fix.

Who can relax: Organizations without Ivanti Connect Secure; 22.7.x and earlier is reported not affected (end of life January 31, 2027), and 25.1.3.0 or later is reported not affected by the October 29 CVEs.

Affected
Ivanti Connect Secure 25.1.1.2 and prior, 25.1.2.2 and prior, 22.8R2.5 and prior (CISA, updated Oct 30)
CVE-2026-104935: 25.1.1.1 and prior, 25.1.2.2 and prior, 22.8R2.4 and prior
CVE-2026-111357 and CVE-2026-118527: 25.1.1.2 and prior, 22.8R2.5 and prior (per Ivanti's advisory as reported by CiphersSecurity)
Fixed in
Ivanti Connect Secure 25.1.1.3 and 22.8R2.6 fix all three CVEs (per Ivanti's advisory as reported by CiphersSecurity)
25.1.3.0 and later (fixes CVE-2026-104935; reported not affected by the other two)
Confirm the build for your hardware in Ivanti's advisory
CVSS
8.6 (v3.1, CNA)
EPSS
88.9% (percentile 99.8)
CISA KEV
Yes, listed as known exploited
Exploitation
Exploited in the wild
Severity
Critical

What to do

  1. Upgrade to 25.1.1.3 or 22.8R2.6 (or 25.1.3.x on supported hardware), even if you already applied the October 13 fix
  2. Do not rely on the Integrity Checker Tool alone; capture memory and network evidence if exposure dates overlap October 1 or later
  3. Hunt welcome.cgi requests whose X-DSCGI-PATH header does not match the URL path
  4. Rotate credentials that passed through the VPN, including AD service accounts, since the actor harvested NTLM hashes and ran Kerberoasting
  5. If compromise is suspected, follow CISA's recovery steps: back up config, factory reset or rebuild, upgrade, restore, and reset all passwords, certificates and API keys
  6. Restrict ICS admin interfaces and alert on outbound connections from the appliance

How to check if you are affected or compromised

  • Search web logs for high volumes of requests to /dana-na/auth/url_default/welcome.cgi
  • Look for files in /tmp/ (ml.py, rq5.py, mk.py, rr.py, sp_out.txt, spray_hits.json) and /data/.icscap/
  • Look for a process named dsstatmond (renamed tcpdump) and tampering in debuglog or audit.log
  • Check traffic to 108.165.147[.]64 and for LDAP queries pulling LAPS or BitLocker attributes from the ICS address

What happened#

Update, October 31: The missing link is now patched, and the patch means upgrading again. Volexity's post was updated to say that "on October 29, 2026, Ivanti published a patch" for the privilege escalation, tracked as CVE-2026-111357. The CVE record describes how the dsinvoked broker trusts DSCache data, "leading to privilege escalation to root, as exploited in the wild in October 2026," and scores it CVSS 3.1 7.0. Ivanti also fixed CVE-2026-118527, which the KEV entry describes as predictable identifiers that let "a remote authenticated attacker" upload attacker-controlled files "to a known location on disk." CISA lists both as chainable with CVE-2026-104935. On October 30 CISA added both to KEV, with federal due dates of November 2 for CVE-2026-111357 and November 13 for CVE-2026-118527. CISA's updated alert now lists 25.1.1.2 and prior, 25.1.2.2 and prior, and 22.8R2.5 and prior as affected. That means the builds many teams installed for the October 13 fix are vulnerable again. According to CiphersSecurity, citing Ivanti's advisory (revised October 29), 25.1.1.3 and 22.8R2.6 fix all three CVEs, 25.1.3.0 and later is not affected by the two new ones, and there is no workaround. Ivanti's advisory page still did not load for us, so check those builds against it.

On October 13, 2026, Ivanti disclosed CVE-2026-104935 in Connect Secure (ICS), its SSL VPN. The CVE record describes "authentication bypass by spoofing in ICS before version 25.1.3.0" that "allows a remote unauthenticated attacker to execute arbitrary commands." Ivanti's CNA score is CVSS 3.1 8.6, which reads low for unauthenticated command execution. Ivanti's October security update says it is "aware of limited exploitation in the wild" and tells affected customers to "act immediately." CISA added the flaw to the KEV catalog the same day, with a three-day federal deadline and a forensic-triage requirement.

Volexity, which found and reported the flaw, saw exploitation from October 3 against a customer's ICS that was fully patched at 22.8R2.4. The chain combined an authentication bypass in welcome.cgi, a file write and race condition in wu.cgi, and a privilege escalation in which the dsinvoked broker trusts DSCache data, yielding root. Ivanti fixed the first two under this CVE on October 13. The privilege escalation was fixed on October 29 as CVE-2026-111357 (see the update above). Defused reportedly saw first activity on October 1, per BleepingComputer.

Volexity tracks the actor as UTA0576, a previously unknown group. It assesses with low confidence that the motive is criminal, and with medium confidence that the actor uses LLMs in its tooling. After getting in, the actor captured packets to harvest credentials and NTLM hashes, ran Kerberoasting and password spraying, and queried LDAP for LAPS passwords and BitLocker keys.

Who is affected#

As of October 30, CISA lists Connect Secure 25.1.1.2 and prior, 25.1.2.2 and prior, and 22.8R2.5 and prior as affected by the chain. The original October 13 scope for CVE-2026-104935 alone was 22.8R2.4 and earlier, 25.1.2.2 and earlier, and 25.1.1.1 and earlier, per BleepingComputer. NVD says 22.7R2.14 or earlier is not impacted, and CISA notes that 22.8 reaches end of life on January 31, 2027. Ivanti's advisory page would not load for us, so confirm the fixed build for your branch there. Shadowserver tracked more than 5,500 exposed ICS instances, per BleepingComputer.

Do you really need to act?#

Yes, if you run ICS. It is reachable without credentials on the device's public face, and it worked against a fully patched appliance. Two details raise the stakes beyond a normal patch cycle. First, the chain patches a library in memory only and restores the cache entry, so Ivanti's Integrity Checker Tool did not detect the compromise; Volexity says forensic investigation is required. Second, the actor "deployed no malware or web shell" and re-exploited the device for each command, so there may be no persistent implant to find. Exploitation is described as limited. With all three links now public and fixed, expect others to rebuild the chain by diffing patches. Given Ivanti's history (BleepingComputer counts 36 Ivanti CVEs in KEV since 2021), plan for that to change.

What to do now#

  1. Upgrade to 25.1.1.3 or 22.8R2.6, or to 25.1.3.x on hardware that supports it. Do this even if you installed 22.8R2.5 or 25.1.1.2 on October 13. Plan the move off 22.8 before its January 31, 2027 end of life.
  2. If the appliance was exposed on or after October 1, capture memory and packet data before or alongside the upgrade. Do not treat a clean ICT result as clearance.
  3. Rotate credentials that authenticated through or to the VPN, AD service accounts exposed to Kerberoasting, and any LAPS or BitLocker secrets the ICS service account could read.
  4. If you suspect compromise, follow CISA's recovery steps: back up the configuration, factory reset (or rebuild virtual and cloud instances), upgrade, restore the configuration, then reset all domain, admin and local passwords and revoke and reissue stored certificates, API keys and license server credentials.
  5. Alert on outbound connections and LDAP queries originating from the ICS appliance.

How to tell if you were hit#

Volexity's indicators: many requests to /dana-na/auth/url_default/welcome.cgi with an X-DSCGI-PATH header pointing at /home/webserver/htdocs/dana/fb/smb/wu.cgi or /home/runtime/tmp/; files such as /tmp/ml.py, /tmp/mk.py, /tmp/rr.py, /tmp/spray_hits.json and /data/.icscap/h.py; a dsstatmond process (renamed tcpdump); ics-root-run-inband-*.pl under /home/runtime/tmp/; tampering in debuglog and audit.log; and contact with 108.165.147[.]64. On the internal side, look for spraying, Kerberos service-ticket requests and LDAP reads originating from the appliance's IP.

Timeline#

  • — First signs of activity, per Defused.
  • — Exploitation observed by Volexity on a fully patched 22.8R2.4 appliance.
  • — Volexity begins its investigation.
  • — Ivanti discloses and patches; CISA adds the CVE to KEV.
  • — Privilege escalation in the chain still unpatched.
  • — Ivanti revises its advisory and ships 25.1.1.3 and 22.8R2.6, fixing CVE-2026-111357 (privilege escalation to root) and CVE-2026-118527.
  • — CISA adds both CVEs to KEV (federal due dates Nov 2 and Nov 13) and widens the affected range to include 22.8R2.5 and 25.1.1.2.

Vulnerability records

  • CVE-2026-104935 · KEV 2026-10-13 · Authentication bypass by spoofing in ICS before version 25.1.3.0 allows a remote unauthenticated attacker to execute arbitrary commands.
  • CVE-2026-111357 · KEV 2026-10-30 · Ivanti Connect Secure 22.8R2.4 mishandles the manner in which the dsinvoked broker trusts DSCache configuration data, leading to privilege escalation to root…
  • CVE-2026-118527 · KEV 2026-10-30 · Use of predictable filenames in Ivanti Connect Secure before versions 25.1.1.3 and 22.8R2.6 allows a remote authenticated attacker to upload files with…

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. NVD — CVE-2026-104935 nvd.nist.gov
  2. NVD — CVE-2026-111357 nvd.nist.gov
  3. CISA — CISA Urges Patching Newly Exploited Vulnerabilities in Ivanti Connect Secure (updated Oct 30) cisa.gov
  4. CISA — CISA Adds Two Known Exploited Vulnerabilities to Catalog (Oct 30) cisa.gov
  5. Ivanti — October 2026 Security Update ivanti.com
  6. Volexity — A Series of Unauthenticated Events: Chained Exploitation of Ivanti Connect Secure Zero-Days volexity.com
  7. CISA — Known Exploited Vulnerabilities catalog (JSON feed) cisa.gov
  8. CiphersSecurity — Ivanti Connect Secure CVE-2026-111357: Patch And Detect cipherssecurity.com

Coverage and analysis

  1. BleepingComputer — Ivanti warns of Connect Secure zero-day exploited in attacks bleepingcomputer.com