Plan this weekVulnerabilities

Ivanti Connect Secure VPN: CISA now lists two more flaws from an exploited attack chain

On 30 Oct 2026 CISA added CVE-2026-111357 and CVE-2026-118527, both in Ivanti Connect Secure, to its list of exploited vulnerabilities. They belong to a chain that Volexity says has been used since early October, and a press report says part of it had no fix yet. We cover it late. Who is affected and what to check.

How urgent

Plan this week

Who is affected

Organisations that run Ivanti Connect Secure, a VPN gateway for remote access. For the first flaw of the chain (CVE-2026-104935), press reports list versions 22.8R2.4 and earlier, 25.1.2.2 and earlier, and 25.1.1.1 and earlier. This does not concern you if you do not run these appliances

What to do

If you run Ivanti Connect Secure, apply the updates in Ivanti's advisory now, then check for signs of intrusion going back to early October. Do not rely only on Ivanti's Integrity Checker Tool, and rotate credentials the VPN could reach if you find signs

Published 31 Oct 2026 · Sources last checked 31 Oct 2026No. 31 / 87

What happened

On 30 October 2026 the US cyber agency CISA added two Ivanti Connect Secure flaws to its Known Exploited VulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary list, which is its record of flaws it has evidence of being used in real attacks:

  • CVE-2026-111357, described as "missing authentication for critical function".
  • CVE-2026-118527, described as "generation of predictable numbers or identifiers".

Ivanti Connect Secure is a VPNVPN A private encrypted tunnel between your device and a network, so traffic does not travel in the open. Tap again to open the glossary gateway that lets staff connect to a company network from outside. We covered none of this earlier, so we are catching up.

The wider story

On 13 October 2026 Ivanti warned of a flaw in the same product, CVE-2026-104935, an authentication bypass that lets a remote attacker with no login run commands on the appliance. BleepingComputer says Ivanti described "limited exploitation in the wild". The security firm Volexity reported that an actor it tracks as UTA0576 had chained it with two other flaws since at least 3 October to get code running as the system's top-level user, even on fully updated devices. Another firm, Defused, saw first signs on 1 October.

Cybersecurity Dive and BleepingComputer both say that Ivanti had patched two parts of the chain and was still working on a third, a privilege escalation. We do not know how the two flaws CISA listed on 30 October map onto that chain. CISA's entries say they are linked, but we could not read Ivanti's advisory, so we cannot say which of them is the third part or whether it is now fixed.

What the attackers did

According to Volexity, as reported by BleepingComputer, the actor left no malwareMalware Any software made to do harm, such as stealing data, spying, locking files or giving an attacker control of a device. Tap again to open the glossary or web shell. It re-used the flaw for each command, tampered with logs and avoided Ivanti's Integrity Checker Tool. BleepingComputer's account, and CISA according to Cybersecurity Dive, say the tool may not reliably detect this activity because the commands run in memory.

Who is affected

Only organisations that run Ivanti Connect Secure. For the first flaw, BleepingComputer lists these versions as affected: 22.8R2.4 and earlier, 25.1.2.2 and earlier, and 25.1.1.1 and earlier. Shadowserver tracks more than 5,500 of these appliances reachable from the internet; that is a count of exposed devices, not of compromised ones. If you do not run one, this story does not concern you.

What to do

This is our reading of press reports and CISA's alert; use Ivanti's advisory for the details.

  1. Find out if you run Ivanti Connect Secure. Ask whoever manages your network or VPN.
  2. Apply the updates in Ivanti's advisory. The press reports we read do not agree on the fixed version numbers, so take them from Ivanti.
  3. Look for signs of intrusion back to early October. The reports say the attacker erased traces from the appliance's logs, so check logs kept elsewhere, such as a central log server, and consider a forensic review.
  4. Do not rely on the Integrity Checker Tool alone. The reports say it may miss this activity.
  5. If you find signs, rotate the passwords, keys and tokens that the VPN could reach. This is general advice from us, not from Ivanti.
  6. Follow Ivanti's notices for the fix of the remaining part of the chain, if it is not out yet.

If you build with AI tools

Our advice, not from the sources: a VPN gateway sits in front of everything behind it, including the servers that hold your keys and deploy secretsSecret (API key, token, password) Any piece of text that proves to a service that you are allowed in, such as an API key, a database password or an access token. Tap again to open the glossary. Keep a list of such devices, who looks after each one, and subscribe to the maker's security notices.

What we could not confirm

We read CISA's alert and two press reports from 13 and 14 October. We did not read Ivanti's own advisory or Volexity's report, so version numbers and the link between the new CVEs and the unpatched part come from press reports and CISA's short entries. CISA's page gives no remediation due date. We do not know how many appliances were compromised, and we have not tested anything.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks