Skip to content
COR Intelligence
Back to The Patch Wave
The Patch WaveThis weekFound by: people

Ivanti VPNs: attackers chained three flaws, and October's fix needs a second update

COR Solutions2 November 2026
5 min read1,085 words

If your VPN was updated in mid October, it still needs another update. Attackers chained three Ivanti VPN flaws to get full control. Firms on 22.8R2.5 or 25.1.1.2 need to update again.

  • Updated 04/11/2026: severity changed from Critical to High, as none of the three flaws scores in the Critical band (Ivanti scores them 8.6, 8.8 and 4.3). The developer section now also gives the CVE record's own score for the second flaw.
A person seen from behind works on a silver laptop beside a rain-speckled sash window, with a small router and navy mug on the wooden desk.

What happened

If your VPN was updated in mid October, it still needs another update. Attackers found a way into Ivanti Connect Secure, a VPN box firms use so staff can log in from home. They chained three flaws together to take full control of the box without a password, then went looking for staff passwords and other secrets on the office network. Ivanti fixed the first flaw on 13/10/2026 and the last two on 29/10/2026, so a box updated in mid October still needs another update.

Does this affect you

Only if your firm, or your IT company, runs an Ivanti Connect Secure VPN. If you're not sure what your remote working VPN is, ask whoever set it up.

What to do

  1. Ask your IT person or IT company: "Do we have Ivanti Connect Secure, and what version is it on?"
  2. It needs to be on 22.8R2.6, 25.1.1.3 or 25.1.3.1 or later. Versions 22.8R2.5 and 25.1.1.2, the mid October fix, are not enough.
  3. A box on any 25.1.2 version is not safe, even though its number looks higher than 25.1.1.3. Ivanti's only fix for that line is a move to 25.1.3, and Ivanti says that needs its newer ISA4500, ISA6500 or ISA8500 hardware, or a virtual box rebuilt from its 25.1.3.0 template.
  4. On 22.8, Ivanti recommends going to 25.1.1.3, as it says 22.8 is only meant as a temporary bridge to 25.1. 22.8R2.6 is the fix if that move can't happen straight away.
  5. Ask them to check the box for signs it was broken into before the update. Volexity and CISA both say Ivanti's own checking tool may not spot this attack, and CISA says finding out needs network and memory forensics.
  6. If a break in is suspected, CISA's steps are: back up the box's settings, factory reset it (or rebuild a virtual one) on the latest version, restore the settings, then reset every password, including domain, administrator and local accounts, and replace stored certificates and API keys.

Is it being attacked?

Yes. Volexity saw attacks from 03/10/2026, and CISA lists all three flaws as exploited. Ivanti says it knew of attacks on a limited number of customers when it disclosed the flaws.

Why it keeps happening

VPN boxes sit on the internet and hold the keys to the office network. Volexity also says, with medium confidence, that these attackers used Ai models to help build their attack.

Found by

Volexity found the attacks while investigating a break-in at one of its customers, and worked out the chain with Ivanti. Volexity thanks OpenAI because its "cyber models have allowed Volexity to drastically reduce its analysis time". Volexity credits Ai with speeding up its analysis; it doesn't say Ai found the flaws. Tag: people.

For developers

  • CVE-2026-104935: authentication bypass by spoofing (welcome.cgi routes to arbitrary CGI via the X-DSCGI-PATH header) plus a file write race in wu.cgi, unauthenticated command execution. CVSS 3.1 8.6 (Ivanti). CVE record lists 25.1.3.0, 25.1.3.1 and 22.8R2.5 as unaffected; 22.7R2.14 and earlier not affected. KEV since 13/10/2026.
  • CVE-2026-111357: missing authentication for a critical function. The dsinvoked broker trusts DSCache configuration data, so cgi-server code can make a maintenance task run as root. Ivanti: "allows a local authenticated attacker to escalate their privileges", CVSS 3.1 8.8 (High), CWE-306, CWE-862, CWE-345. CVE record (MITRE, the CNA) names 22.8R2.4, says "exploited in the wild in October 2026" and scores it lower, CVSS 3.1 7.0 (High, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), with CWE-829. KEV since 30/10/2026.
  • CVE-2026-118527: predictable filenames let a remote authenticated attacker upload attacker-controlled files to a known location on disk. Ivanti scores it 4.3 in its advisory and its CVE.org record (published 03/11/2026). KEV since 30/10/2026.
  • Ivanti's tables (advisory updated 29/10/2026): CVE-2026-104935 affects 25.1.1.1 and prior, 25.1.2.2 and prior, 22.8R2.4 and prior, resolved in 25.1.1.2, 25.1.3.0 or 25.1.3.1, and 22.8R2.5. CVE-2026-111357 and CVE-2026-118527 affect 25.1.1.2 and prior and 22.8R2.5 and prior, resolved in 25.1.1.3 and 22.8R2.6. So 22.8R2.5 and 25.1.1.2 fix only CVE-2026-104935, and the 25.1.2 line has no 25.1.2 fix.
  • 25.1.3 migration (Ivanti): 25.1.3.0 was released in July 2026 and runs on ISA4500, ISA6500 or ISA8500; hardware customers need the new physical servers in place, and virtual or cloud customers need new devices built from the 25.1.3.0 template. Ivanti says 25.1.3.0 or later does not contain CVE-2026-104935; the Canadian Cyber Centre (AV26-1035 Update 2) lists the fixed releases as 22.8R2.6, 25.1.1.3 and 25.1.3.1, which is the target used here.
  • 22.7 and 22.8 (Ivanti): 22.7R2.14 and earlier are not affected by CVE-2026-104935; 22.7 reaches end of life on 31/01/2027. For 22.8.X Ivanti recommends 25.1.1.3 or later and calls 22.8 a temporary bridge from 22.7 to 25.1.
  • CISA (alert revised 30/10/2026) lists affected versions as 25.1.1.2 and prior, 25.1.2.2 and prior, and 22.8R2.5 and prior, and urges an immediate update. It warns the Integrity Checker Tool "may not detect evidence of exploitation of CVE-2026-104935 because threat actor commands execute in memory". Recovery: back up the configuration, factory reset and upgrade (rebuild cloud and virtual instances), restore the configuration, reset passwords for all accounts including domain, administrator and local accounts, revoke and reissue stored certificates, reset stored API keys and licence server credentials.
  • Detection (Volexity): many requests to /dana-na/auth/url_default/welcome.cgi with an X-DSCGI-PATH header pointing at wu.cgi or /home/runtime/tmp/; mismatches between URL path and X-DSCGI-PATH; check /tmp. The chain patches libdsplibs.so in memory and cleans debuglog and audit.log, so the Integrity Checker Tool may miss it; memory and network forensics are needed. IOCs on Volexity's GitHub.
  • Threat actor UTA0576 (Volexity, low confidence criminal). Post-exploitation targeted LDAP credentials, LAPS passwords, BitLocker recovery keys, Kerberos testing and password spraying.

Sources

Read next

More from The Patch Wave