Ivanti VPN attacks need more than a patch

Attackers take over Ivanti Connect Secure VPNs; further fixes are available

From the HARD Situation Room · First reported
hub.ivanti.com: Security Advisory Ivanti Connect Secure (CVE-2026-104935)
Screenshot: hub.ivanti.com

CISA added two flaws in the chain to its exploited-vulnerability list on 30 October. NHS England says Ivanti observed attacks affecting a limited number of customers when the three flaws were used together.

What to do

  1. Ask your IT team today.Send this alert to whoever runs remote access for your business or family office. Ask whether you use Connect Secure and request its exact version.
  2. Get the appropriate update installed urgently.Have IT confirm the supported release for your device against Ivanti’s advisory, then report the installed version and completion time.
  3. Request a compromise assessment.Ask the security team to investigate earlier access. A clean integrity check should not be the only evidence used to close the issue.
  4. Escalate signs of an intrusion.Have an incident-response specialist assess recovery and identify any exposed accounts or credentials that need resetting. Ask IT whether staff need to change passwords or use a different approved way to connect.

What happened

If your business or family office uses Ivanti Connect Secure, ask IT for an urgent update and a check for earlier compromise. Attackers have combined flaws to gain root access: full control of the workplace VPN device, without a login. Volexity documented the attack[1].

On 30 October, the US cybersecurity agency CISA added CVE-2026-111357 and CVE-2026-118527 to its list of flaws being exploited. The third flaw, CVE-2026-104935, joined the list on 13 October. Canada’s Cyber Centre confirms both additions[2].

NHS England’s updated advisory[3] says Ivanti observed the three flaws being used together against a limited number of customers. It urges affected organisations to apply the relevant update as soon as possible.

Ivanti Connect SecureCVE-2026-104935 · CVE-2026-111357 · CVE-2026-118527
HARD priority
High Exploitation confirmed
25.1.1 branch
25.1.1.2 and earlier: update to 25.1.1.3
22.8R2 branch
22.8R2.5 and earlier: update to 22.8R2.6
Other versions
Have IT confirm the supported update for the exact device and software branch.
Two affected branches. Version thresholds from the Canadian Cyber Centre’s 30 October update[2]; this is not a complete upgrade matrix.
The full story3 more sections

Who is affected

Connect Secure provides remote access to an organisation’s systems[4]. For staff working from home or travelling, it can be the way into the office network. The affected equipment needs attention from the team running that service.

NHS England[3] also lists 25.1.2.2 and earlier in that software branch as affected. If your version is outside the two rows above, ask IT to check Ivanti’s advisory[5] for the appropriate upgrade path.

Why another update matters

The earlier fix addressed the login-bypass flaw, but did not repair every flaw used in the attack. Volexity’s updated report[1] says Ivanti released the privilege-escalation patch on 29 October. That makes the exact installed version more useful than an assurance that the system was patched sometime this month.

A clean check is not an all-clear

Volexity observed[1] theft of stored credentials and searches for administrator passwords and BitLocker recovery keys. It also warns that Ivanti’s Integrity Checker Tool can miss this attack. A passing check alone cannot rule out compromise.

HARD’s recommendation is to ask two separate questions: has the vulnerable software been fixed, and has someone investigated what happened before the fix?

Timeline
  1. HARD publishes its article, at High.

References9
  1. ^ Volexity (). “A Series of Unauthenticated Events: Chained Exploitation of Ivanti Connect Secure Zero-Days”. Original investigation establishes appliance takeover, credential theft and detection limits; its update confirms the 29 October privilege-escalation patch.
  2. ^ Canadian Centre for Cyber Security (). “Ivanti security advisory (AV26-1035) — Update 2”. Updated advisory confirms all three KEV addition dates and lists affected-version thresholds.
  3. ^ NHS England (). “Ivanti Releases Security Updates for Connect Secure”. Updated advisory identifies affected releases, attributes limited exploitation of the three-flaw chain to Ivanti and urges prompt updates.
  4. ^ Ivanti. “Ivanti Connect Secure VPN Tunneling Configuration Guide”. Establishes Connect Secure’s role in remote access to corporate systems.
  5. ^ Ivanti. “Security Advisory Ivanti Connect Secure (CVE-2026-104935)”. Canonical advisory linked for IT; retrieval returned 403, so version claims rely on the readable government advisories below.
  6. CISA (). “CISA Adds Two Known Exploited Vulnerabilities to Catalog”. Confirms the two additions based on active exploitation; read through the Déjà Vu mirror because direct retrieval failed.
  7. CISA via Déjà Vu (). “CISA alert reproduced through Déjà Vu”. Readable reproduction of the supplied CISA alert, independently corroborated by the Canadian advisory.
  8. The Hacker News (). “Attackers Chain Three Ivanti Connect Secure Flaws to Gain Unauthenticated Root Access”. Supplied report read for cross-checking; later than the draft cutoff and not used as sole support for publication claims.
  9. Rapid7 (). “Additional Ivanti Connect Secure zero-days exploited in the wild (CVE-2026-111357, CVE-2026-118527)”. Supplied report read to cross-check fixes and identify discrepancies; later than the draft cutoff.

Situation Room articles are updated as events develop: updates are added to the timeline, and never edited away. Follow them by email or RSS.