Patching on day one is the standard advice for edge devices. This week’s Ivanti news shows the limit of that advice. Volexity reports that an attacker used a chain of three zero-days against an appliance that was fully patched at the time, and the lesson for Ivanti Connect Secure zero-day VPN security is that a patch plan alone is not enough. You also need a plan for the day you find out the box was already owned.
What Volexity Found
In its October 13, 2026 report, Volexity says that in the first week of October it “discovered an unknown threat actor, UTA0576, abusing a zero-day exploit chain to compromise a fully patched (at the time, version 22.8R2.4) Ivanti Connect Secure (ICS) VPN appliance.” The chain “combined an authentication bypass, a remote code execution (RCE), and a privilege escalation vulnerability to achieve unauthenticated root-level code execution.”
Two details matter. First, “fully patched” describes that one appliance at that moment. Volexity describes a single investigation at one customer, and I am not claiming this was a broad campaign. Second, Volexity says exploitation began on October 3, 2026, and that it started its investigation on October 5.
After getting in, Volexity says UTA0576 “primarily focused on credential theft, data exfiltration, log tampering, and network reconnaissance.” It lists:
- Extracting credentials stored on the appliance, “such as domain credentials used with LDAP.”
- Searching Active Directory for LAPS local administrator passwords and BitLocker recovery keys.
- Password spraying and packet capture of LDAP traffic from the appliance.
- Removing entries from the appliance’s debug log and Linux audit log.
SecurityWeek adds Volexity’s view that the actions pointed to “preparation for lateral movement and a wider compromise of the network.” Volexity found no backdoor or web shell, because, as Volexity puts it, it “did not identify first-stage malware or web shells that would have enabled the threat actor to execute commands without re-exploiting” the appliance. The entire chain ran for each command, with results returned in the HTTP response.
That is why detection is hard. Volexity says Ivanti’s Integrity Checker Tool “does not detect any modifications” because the exploit patches code in memory and restores configuration data afterward. “As such, forensic investigation is required to identify evidence of exploitation.”
Ivanti Connect Secure Zero-Day VPN Security: What Is Patched as of October 15
Ivanti is tracking the authentication bypass and the RCE under CVE-2026-104935. SecurityWeek reports those are patched in ICS versions 22.8R2.5, 25.1.1.2, 25.1.3.0 and 25.1.3.1. Ivanti’s own October Patch Tuesday post lists the same fixed builds and says Ivanti is “aware of limited exploitation.”
The third flaw is a privilege escalation in how the dsinvoked service trusts DSCache configuration data. Volexity says “Ivanti is working on a fix for the privilege escalation vulnerability, and it will be included in a future release in the coming weeks.” SecurityWeek says it “remains unpatched.” Ivanti’s post describes “a fix for a related privilege escalation flaw used in the same chain” as “due in the coming weeks.” I checked again today, October 15, and found no report of a released fix. I could not read Ivanti’s advisory page itself, which is a script-loaded page, so that status rests on Volexity, SecurityWeek and Ivanti’s blog. Verify it on Ivanti’s site before you act.
Do not tell your leadership “all three are patched.” Two are. The third is, by these sources, still open.
What CISA Says
In its October 13 alert, CISA says it “added CVE-2026-104935 to its Known Exploited Vulnerabilities (KEV) Catalog on Oct. 13, 2026,” and that “Organizations seeking to determine whether they were compromised will need to conduct network and memory forensics.” The KEV entry in CISA’s catalog data lists a due date of October 16, 2026. For suspected compromise, CISA recommends actions from Ivanti’s recovery procedures: back up the configuration, “conduct a factory reset and upgrade the appliance to the latest version” (rebuild virtual instances), restore the configuration, and “reset passwords for all accounts, including domain, administrator, and local accounts,” plus revoke and reissue stored certificates and reset stored API keys.
CISA also notes that “Ivanti Connect Secure version 22.8 reaches end of life on Jan. 31, 2027,” which Ivanti’s post echoes while recommending a move to 25.x.
A note on other vendors. Ivanti’s Patch Tuesday post says edge devices “dominated the weeks before this Patch Tuesday,” citing a Citrix NetScaler zero-day and a SonicWall SMA1000 flaw. SecurityWeek separately reports exploitation attempts against SonicWall’s CVE-2026-102255 starting October 8, after an October 6 disclosure. None of those sources ties these cases to the Ivanti activity, so treat them as a pattern of edge-device attention, not one campaign.
My Compromise Plan for a Remote Access Appliance
This checklist is my own recommendation. The sources above do not prescribe it, apart from the CISA recovery steps already quoted.
- Patch now, then assume nothing. Apply the fixed build for your code line. Treat the patch as closing the door, not as proof nobody came through it.
- Hunt back to early October. Volexity suggests watching for large numbers of requests to welcome.cgi and for mismatches between the URL path and the X-DSCGI-PATH header, and checking /tmp for post-exploitation files.
- Look for movement from the appliance. Volexity says systems showing “attempts to move laterally originating from the ICS VPN device” should be forensically investigated. Review directory service queries and logins from the appliance’s service account.
- Plan the credential reset before you need it. The appliance can hold domain credentials. Know which service accounts it uses and how you would rotate them, along with certificates and keys.
- Limit what the box can reach. Give its service account least privilege and put internal segmentation behind it, so root on the appliance is not a master key.
- Keep logs off the box. Volexity says the attacker edited local logs. Forward logs and network telemetry elsewhere.
- Rehearse a rebuild. Know who can factory reset and reload the appliance, how long it takes, and what remote access you offer meanwhile.
- Know your end-of-life dates. If you run 22.8, plan the move to 25.x now.
The Takeaway
This is my view: a patch plan answers “are we on the latest version?” A compromise plan answers “if this box were owned last week, would we know, and what would we do?” For the device sitting at your network edge, you need both, and this week’s reporting shows why.
