The U.S. Cybersecurity and Infrastructure Security Agency has added two additional security vulnerabilities impacting Ivanti Connect Secure to its heavily watched Known Exploited Vulnerabilities catalog. This urgent update arrives in the wake of active, malicious exploitation observed in enterprise environments, prompting heightened vigilance across both federal networks and the broader private sector.
These newly cataloged security flaws are intrinsically linked to a sophisticated, multi-stage exploit chain that first came to light earlier in the month. Security researchers at Volexity documented how this dangerous chain was actively weaponized by a previously undocumented and highly targeted threat actor tracking under the internal moniker UTA0576.
The campaign initially made headlines when the threat group combined these vulnerabilities with an authentication bypass flaw designated as CVE-2026-104935, which carries a critical CVSS score of 8.6. Recognizing the severity of that initial entry point, CISA swiftly added CVE-2026-104935 to its KEV catalog on October 13, 2026, forcing immediate federal remediation efforts.
According to technical analysis published by Volexity, the threat actors executed a meticulously planned sequence of events. The exploit chain combined an initial authentication bypass mechanism, a remote code execution vector, and a local privilege escalation vulnerability to successfully achieve unauthenticated, root-level code execution on targeted Ivanti Connect Secure appliances.

Unlike traditional cyberattacks that typically leverage such high-level access to deploy persistent web shells, ransom-demanding ransomware, or secondary payload malware, the activity surrounding UTA0576 deviated from expected norms. Investigators observed the adversary utilizing their privileged access for deeper espionage and foundational persistence objectives. Specifically, the threat actor focused heavily on extracting sensitive credentials, harvesting limited Active Directory metadata, conducting comprehensive host reconnaissance, and aggressively hunting for administrator passwords alongside BitLocker recovery keys.
Ivanti addressed the unfolding situation by detailing the complex engineering timeline required to remediate the multi-component attack chain. Around the time security researchers first publicized the campaign, Ivanti was actively developing and testing fixes for the local privilege escalation vulnerability leveraged within the sequence. Patches for both newly cataloged flaws are now fully available across supported versions of Ivanti Connect Secure.
Providing transparency into their patching decisions, Ivanti explained that at the exact time exploitation was discovered, a fix for the primary authentication bypass flaw was already undergoing quality assurance testing for supported product versions. When the subsequent local privilege escalation vector was uncovered, software engineers made the operational decision not to delay the deployment of the primary fix. Their primary focus remained centered on mitigating the initial vector to protect customers from the most immediate exploitation path as quickly as possible.
Furthermore, Ivanti disclosed that a portion of these underlying vulnerabilities had actually been identified internally as part of the company’s proactive product security program. A partial remediation was previously addressed and patched in the July software release version 25.1.3.0. Following that release, developers had been actively working to backport the security fixes to other supported iterations of the software when the active exploitation activity materialized in the wild.
The latest round of software releases comprehensively addresses all the individual vulnerabilities that were successfully chained and exploited by malicious actors. In response to the updated KEV catalog listings, stringent federal directives have been issued for government networks. Federal Civilian Executive Branch agencies are now legally and operationally required to apply the necessary security updates within strict timelines, mandating remediation for the first newly listed flaw by November 2, 2026, and the second by November 13, 2026.
