Skip to content

Back to the catalog

Ivanti Zero-Day Chain Gave Attackers Root Access to Fully Patched VPN
securityweek.comarticle

Ivanti Zero-Day Chain Gave Attackers Root Access to Fully Patched VPN

Ivanti disclosed CVE-2026-104935, an authentication bypass plus RCE in Connect Secure VPN appliances, exploited in the wild; patched in ICS 22.8R2.5, 25.1.1.2, 25.1.3.0 and 25.1.3.1. Volexity found threat actor UTA0576 chained three zero-days, including a still-unpatched privilege escalation, to get unauthenticated root on a fully patched appliance. Post-exploitation focused on stealing domain credentials, Active Directory reconnaissance (LAPS passwords, BitLocker keys), password spraying, a custom Kerberos tool and log tampering. Volexity assesses with medium confidence that the actor uses LLMs for exploit development.

TL;DR Ivanti Connect Secure zero-day chain (CVE-2026-104935 plus an unpatched privesc) exploited by UTA0576 for root access and AD credential theft, per Volexity.
Document

What it is

CVE-2026-104935 is a high-severity flaw in Ivanti Connect Secure (ICS) VPN appliances. It covers two bugs: an authentication bypass and a remote code execution bug. Together they let a remote, unauthenticated attacker run arbitrary commands. Ivanti says exploitation has hit a limited number of customers. Volexity found it while investigating an incident at one of its customers, and dates the earliest exploitation to October 3.

How it works

Volexity says threat actor UTA0576 chained three zero-days to get unauthenticated, root-level code execution on a fully patched ICS appliance. The CVE covers two of them. The third, a privilege escalation, has no patch yet. The page gives no further technical detail on any of the three.

Preconditions / Affected

  • The target is an ICS appliance running a version before the fixed builds below.
  • A patched appliance is still exposed to the privilege escalation, so patching closes only part of the chain.

What to do

  • Upgrade to ICS 22.8R2.5, 25.1.1.2, 25.1.3.0 or 25.1.3.1.
  • Ivanti plans to fix the privilege escalation "over the coming weeks". The page names no workaround or mitigation for it, and it publishes no indicators of compromise.
  • The page lists what the attackers did after gaining access, which is useful for scoping a hunt:
  • They took domain credentials stored on the appliance.
  • They exfiltrated limited Active Directory metadata.
  • A custom tool searched Active Directory for LAPS passwords and BitLocker recovery keys.
  • They ran password spraying and tested credentials with a custom Kerberos tool.
  • They tried to pull credentials from captured network traffic.
  • They scanned the network and collected the appliance's configuration data.
  • They parsed authentication logs to find valid usernames.
  • The page doesn't spell out remediation, but it implies that any credentials the appliance held, and any LAPS or BitLocker secrets reachable from it, should be treated as exposed on a suspect device.

Caveats

  • Volexity found no backdoor or web shell on the device, so a clean file check is not evidence of a clean appliance.
  • The intrusion was disrupted before the attackers' goals were clear. Volexity believes with high confidence that the activity was preparation for lateral movement and wider compromise.
  • Motivation is assessed with low confidence as criminal rather than espionage.
  • The assessment that UTA0576 uses LLMs for exploit development and post-exploitation is medium confidence.

CVEs named here

Technologies named here

Techniques named here

  • Active Directory metadata exfiltration
  • Password spraying
  • Credential testing with a custom Kerberos tool
  • Network scanning
  • Collection of appliance configuration data
  • Parsing authentication logs to identify valid usernames
  • Log tampering
  • Credential theft

Threat actors named here