Ivanti Connect Secure Zero-Day Exploited in Chained Attack

Attackers exploited an authentication bypass in Ivanti Connect Secure VPNs before a patch existed, chaining it with a privilege escalation bug that Ivanti fixed later in October.

Coiled yellow Ethernet network cables with RJ45 connectors on a white background
Coiled yellow Ethernet network cables with RJ45 connectors on a white background
In this article
  1. What is CVE-2026-104935?
  2. Affected and fixed versions
  3. How the attack worked
  4. The second flaw (patched since)
  5. What administrators should do
  6. Why it matters for everyone else
  7. Bottom line

Update, November 20, 2026: Ivanti has since fixed the second flaw described below, now tracked as CVE-2026-111357. CISA added it to its Known Exploited Vulnerabilities catalog on October 30 and gave federal agencies until November 2 to patch. If you run Connect Secure, install Ivanti's latest release. The original report from October 17 follows.

Attackers have exploited a zero-day vulnerability in Ivanti Connect Secure, the enterprise VPN used by many companies and government agencies, to break into networks without a password. Ivanti disclosed the flaw, tracked as CVE-2026-104935, on October 13 and released fixes, but researchers say the attackers chained it with a second, privilege-escalation bug that is still unpatched. According to Rapid7, administrators should patch on an emergency basis and check for signs of compromise.

What is CVE-2026-104935?

Rapid7 describes CVE-2026-104935 as an authentication bypass by spoofing with a CVSS score of 8.6. It lets a remote, unauthenticated attacker execute arbitrary commands on an Ivanti Connect Secure appliance. Ivanti says exploitation happened before disclosure and affected a limited number of customers. CISA added the bug to its Known Exploited Vulnerabilities catalog the same day.

Rapid7 also notes that part of the issue had already been fixed in Ivanti's July release (25.1.3.0) through its internal security program, and attackers struck while Ivanti was still bringing that fix to other supported versions.

Affected and fixed versions

StatusIvanti Connect Secure versions
Affected25.1.1.1 and earlier, 25.1.2.2 and earlier, 22.8R2.4 and earlier (in their respective code lines)
Fixed25.1.1.2, 25.1.3.0, 25.1.3.1 and 22.8R2.5
Not affected22.7.x and earlier, per Ivanti's advisory

Full details are in Ivanti's security advisory.

How the attack worked

Security firm Volexity, which detected the activity, published a detailed analysis of the intrusions. It says exploitation began on October 3 and that the first victim it investigated was running a fully patched appliance at the time. The attackers chained three weaknesses, including the authentication bypass and the still-unpatched privilege escalation, to gain root access without logging in.

Once inside, according to Volexity, the attackers:

  • stole credentials stored on the VPN appliance, including domain accounts used for LDAP;
  • searched Active Directory for local administrator passwords and BitLocker recovery keys;
  • ran password spraying and Kerberoasting attacks to obtain more credentials;
  • tampered with logs and reverted changes to hide their tracks, without installing a web shell.

Volexity tracks the group as UTA0576 and assesses with low confidence that it is criminally motivated rather than focused on espionage. It also assesses, with medium confidence, that the attackers used large language models to help develop the exploit and carry out post-exploitation work.

The second flaw (patched since)

The privilege escalation bug abuses how a Connect Secure component trusts cached configuration data, letting commands run as root. Ivanti is working on a fix that Volexity says will arrive "in the coming weeks." Patching CVE-2026-104935 blocks the unauthenticated entry point in this chain, but it does not fix the escalation bug itself.

Volexity also warns that Ivanti's Integrity Checker Tool "may not be able to identify device compromise," because the attack modifies code only in memory and restores configuration data afterward.

What administrators should do

  1. Upgrade to a fixed release immediately, outside normal patch cycles.
  2. Hunt for compromise even after patching, using the indicators Volexity has published.
  3. If you suspect a breach, follow Ivanti's recovery steps and assume credentials stored on or passing through the appliance are exposed. Reset them, including LDAP service accounts.
  4. Review Active Directory for signs of Kerberoasting and password spraying.

Why it matters for everyone else

VPN appliances are a favorite target because they sit on the edge of the network and hold the keys to everything behind it. When those keys are stolen, the damage shows up as account takeovers and leaked passwords far from the original breach. If you're an employee rather than an admin, it is a good moment to check whether your passwords have been leaked and make sure two-factor authentication is turned on.

Bottom line

This is the latest in a long line of attacks on Ivanti VPN gear, and the unpatched second flaw means the story isn't over. Patch now, hunt for intrusions and watch for Ivanti's follow-up fix.

Source: Rapid7

Add The Tech Wonder as a preferred source on Google

The Tech Wonder Team

Editorial team

The Tech Wonder covers technology news and writes practical, plain-English guides to the gadgets, apps and ideas shaping everyday life.

0 Comments

Join the discussion. Comments are moderated and your email is never published.

Around the web