UTA0576 Chained Three Ivanti Zero-Days for Root Access: Why a Patched VPN May Still Be a Compromised VPN

A patch can close a vulnerability. It cannot prove that attackers did not already use it.
That distinction matters for organizations running Ivanti Connect Secure (ICS). In October 2026, threat intelligence firm Volexity reported that threat actor UTA0576 chained three vulnerabilities to gain unauthenticated, root-level access to an ICS appliance. The attacker then targeted credentials and Active Directory data. Assets that can open doors well beyond the VPN itself.
CISA added all three vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog. Its guidance calls for more than routine patching when compromise is suspected: investigate, then reset or rebuild the appliance, upgrade it, and rotate credentials.
For organizations, the operational question is not simply, “Did we install the update?” It is, “Can we trust the appliance, and the access that passed through it?”
HOW THE THREE-VULNERABILITY CHAIN WORKS
The three flaws affect different parts of the attack path:
- CVE-2026-104935 enabled an authentication bypass leading to remote code execution.
- CVE-2026-111357 enabled privilege escalation.
- CVE-2026-118527 involved predictable filenames that allowed an authenticated attacker to upload attacker-controlled files to a known location.
Chained together, the vulnerabilities allowed an unauthenticated attacker to execute commands as root on the appliance. That is not the same as saying each flaw independently provides unauthenticated root access; it is the combined chain that creates the severe outcome.
Volexity reported that UTA0576 used the access to extract credentials stored on the device, examine Active Directory, and search for sensitive information such as local administrator passwords and BitLocker recovery keys. The investigation also identified log tampering and activity that could support further movement inside the victim’s network.
Read the technical investigation from Volexity and the vendor’s Ivanti security advisory.
WHY PATCHING MAY NOT BE THE END OF THE RESPONSE
Updating an affected appliance is essential. But installing a fixed version after an attacker has accessed the old one does not automatically remove every consequence of that access.
A compromised VPN appliance sits at a critical trust boundary. It can handle remote-user connections, authentication data, and traffic to internal resources. If an attacker obtains privileged access there, they may be able to steal credentials or use them against other systems. The appliance can be patched and still require a full recovery process.
A clean result from a standard integrity check is not definitive proof that exploitation did not occur. CISA says organizations seeking to determine whether they were compromised may need network and memory forensics. The agency also warns that Ivanti’s Integrity Checker Tool may not detect evidence of CVE-2026-104935 exploitation because attacker commands can execute in memory.

That is why a patch status report alone cannot answer the incident-response question. Teams need to assess exposure, look for signs of access, and determine whether credentials or downstream systems may also be affected.
ACT NOW: A PRACTICAL IVANTI RESPONSE CHECKLIST
Use this checklist to organize the work. If you suspect exploitation, involve qualified incident-response support and follow current vendor and CISA guidance.
- Identify every relevant appliance. Confirm whether your organization uses Ivanti Connect Secure, including hardware, virtual, and cloud deployments. Check asset inventories, network diagrams, procurement records, and managed-service-provider documentation.
- Confirm the product version and branch. CISA lists affected versions as 25.1.1.2 and prior, 25.1.2.2 and prior, and 22.8R2.5 and prior. Confirm your exact build and deployment type against the Ivanti advisory.
- Upgrade to a fixed release. Ivanti identifies 25.1.1.3 and 22.8R2.6 as fixes for the two additional vulnerabilities disclosed in the chain. Ivanti recommends that customers on the 22.8 line move to 25.1.1.3 or later; 22.8R2.6 is an option for organizations unable to migrate immediately. Confirm the right release and migration path for your platform before deployment.
- Treat suspected compromise as a security incident, not just a patch task. Restrict or isolate the appliance as appropriate, preserve evidence, and arrange network and memory forensics. Do not treat a clean Integrity Checker result as conclusive.
- Reset or rebuild if compromise is suspected. CISA’s recovery guidance calls for a factory reset and upgrade for affected physical appliances; virtual and cloud instances should be rebuilt and upgraded. Preserve evidence and coordinate recovery before resetting, since reset activity can affect what investigators can examine. Follow the CISA alert and Ivanti recovery procedures.
- Rotate credentials and review connected systems. CISA advises resetting passwords for domain, administrator, and local accounts, and revoking and reissuing stored certificates, API keys, and license-server credentials. Review logs and identity activity for signs of lateral movement, unusual authentication, or use of credentials associated with the appliance.
- Check other internet-facing appliances. Review VPNs, firewalls, remote-access gateways, and management interfaces for exposed services, outdated firmware, and incomplete inventories. An edge appliance can become a high-impact foothold when it is both reachable and trusted.

THE DEADLINE IS URGENT, AND THE RISK IS NOT LIMITED TO FEDERAL AGENCIES
CISA’s KEV catalog lists November 2, 2026, as the due date for CVE-2026-111357, and November 13, 2026, for CVE-2026-118527. The catalog entry for CVE-2026-111357 also identifies forensic triage requirements under CISA’s BOD 26-04.
Those federal deadlines apply to covered federal agencies; they do not automatically create the same legal requirement for every private organization. But private organizations should still treat the issue as urgent: exploitation has been reported, the vulnerabilities can be chained, and the appliance may protect access to critical business systems. Do not wait for a deadline that was not written for your organization to determine your response timeline.
BUILD A PROCESS THAT FINDS EDGE EXPOSURE
The Ivanti incident highlights a recurring challenge: organizations cannot patch an appliance they do not know they have, and they cannot manage recovery confidently without knowing what connects to it.
Cenova Cyber’s Vulnerability Management as a Service (VMaaS) helps discover assets, prioritize vulnerabilities based on exposure and risk, coordinate remediation, and validate fixes. Our 24/7 security monitoring combines continuous monitoring with analyst investigation and response, so suspicious activity does not have to wait for the next business day.

PATCH, INVESTIGATE, AND RESTORE TRUST
The Ivanti Connect Secure chain is a reminder that patching and incident response solve different problems. Updates address known vulnerabilities. Investigation helps determine whether attackers exploited them. A reset or rebuild, credential rotation, and review of connected systems can help restore trust when compromise is suspected.
If you are unsure whether your organization has exposed Ivanti appliances, or whether your edge-device inventory is complete, contact Cenova Cyber for a free exposure check. We can help you identify what is exposed, prioritize next steps, and give your team a clearer path to a trusted network.
