ThreatBeaconXSubscribe
CriticalVulnerability · 15 min read

Attackers Chain Three Ivanti Connect Secure Vulnerabilities to Gain Unauthenticated Root Access

Attackers have exploited three vulnerabilities in Ivanti Connect Secure (ICS) appliances by chaining an authentication bypass, remote code execution, and privilege escalation to achieve unauthenticated root-level access. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) added two of the vulnerabilities, CVE-2026-111357 and CVE-2026-118527, to its Known Exploited Vulnerabilities (KEV) catalog on October 30, 2026, following reports of active exploitation. The third vulnerability, CVE-2026-104935, had already been added to the catalog on October 13, 2026. The activity was first documented by cybersecurity company Volexity earlier in October. The company attributed the exploitation to a previously undocumented threat actor tracked as UTA0576. The three vulnerabilities are: CVE-2026-104935 (CVSS 8.6): An authentication-bypass vulnerability associated with the initial access and remote code execution portion of the attack chain. CVE-2026-118527 (CVSS 4.3): A predictable identifier vulnerability that can allow attacker-controlled files to be uploaded to a known location on disk. CVE-2026-111357 (CVSS 8.8): A missing authentication check affecting a critical function, potentially allowing privilege escalation to root. According to Volexity, combining these vulnerabilities allowed UTA0576 to execute commands as root without authenticating to the vulnerable appliance. Unlike attacks that primarily focus on installing web shells or persistent malware, UTA0576 used the compromised VPN appliances to extract stored credentials, collect limited Active Directory metadata, conduct host reconnaissance, and search for administrator passwords and BitLocker recovery keys. Ivanti has released updates addressing all three vulnerabilities. Organizations operating affected Ivanti Connect Secure appliances should upgrade to the appropriate fixed versions and investigate potential compromise rather than relying exclusively on patch installation.

Written by Battula Bhanu prakash·Published Oct 31, 2026

1. Description

Ivanti Connect Secure is an enterprise SSL VPN solution that organizations use to provide secure remote access to internal networks and business resources.

A vulnerability chain affecting Ivanti Connect Secure has enabled attackers to bypass authentication, execute code, and ultimately obtain root-level access to vulnerable appliances.

The exploitation was documented by Volexity, which identified a previously unknown threat actor tracked as UTA0576. The activity was observed against an Ivanti Connect Secure appliance that was fully patched at the time of the initial investigation.

The attack combined three vulnerabilities affecting different stages of the appliance's security controls. The first vulnerability enabled authentication bypass and remote code execution. The second allowed attacker-controlled file content to be uploaded to a predictable location. The third enabled privilege escalation to root.

The resulting chain allowed the attacker to execute commands without valid authentication and access sensitive information stored on or reachable through the appliance.

Volexity observed the actor extracting stored credentials, including LDAP domain credentials, reviewing Active Directory information, searching for administrator passwords and BitLocker recovery keys, and conducting password-spraying activity.

The incident is particularly concerning because Ivanti Connect Secure appliances often operate at the boundary between external users and internal enterprise networks. Compromise of such an appliance can expose authentication material and provide valuable information about the organization's internal environment.

CISA's addition of the vulnerabilities to its KEV catalog further highlights the urgency of remediation.

2. Technical Description

2.1 Ivanti Connect Secure

Ivanti Connect Secure is an enterprise VPN appliance designed to provide remote users with secure access to internal organizational resources.

It acts as an access gateway between external users and internal networks. Depending on its configuration, it may interact with:

  • Active Directory.

  • LDAP authentication services.

  • Enterprise user accounts.

  • VPN authentication systems.

  • Internal applications.

  • Network infrastructure.

  • Privileged administrative services.

Because the appliance can hold or access authentication information, its compromise may expose sensitive credentials and internal directory information.

A vulnerability that provides root-level access to the appliance can therefore create risks beyond the VPN device itself.

2.2 Vulnerabilities involved in the exploit chain

The attack combines three vulnerabilities affecting Ivanti Connect Secure.

CVE-2026-104935 — Authentication bypass and remote code execution

<badge color="danger">CVSS 8.6 — High</badge>

This vulnerability was the initial access component of the exploit chain.

It enabled an attacker to bypass normal authentication protections and execute commands on the appliance. CISA added this vulnerability to its KEV catalog on October 13, 2026.

CVE-2026-118527 — Predictable identifiers

<badge color="warning">CVSS 4.3 — Medium</badge>

This vulnerability involves the generation of predictable numbers or identifiers.

It could allow a remote authenticated attacker to upload files containing attacker-controlled content to a known location on disk.

When combined with the authentication-bypass portion of the attack chain, this weakness contributes to the remote code execution stage.

CVE-2026-111357 — Missing authentication for a critical function

<badge color="danger">CVSS 8.8 — High</badge>

This vulnerability affects a critical function and could allow a local authenticated attacker to escalate privileges.

In the observed exploit chain, it was used to elevate the attacker's execution privileges to root.

CISA added this vulnerability to its KEV catalog on October 30, 2026.

2.3 How the three vulnerabilities work together

The attack relies on chaining vulnerabilities that individually affect different security boundaries.

StageVulnerabilityRole in the attack
Initial accessCVE-2026-104935Authentication bypass and initial remote code execution.
File upload and executionCVE-2026-118527Allows attacker-controlled file content to be written to a predictable location.
Privilege escalationCVE-2026-111357Allows execution to be elevated to root privileges.

According to Volexity, the combined exploitation sequence provides unauthenticated root-level code execution.

This demonstrates why vulnerability assessment should consider the combined impact of multiple flaws rather than evaluating each CVE independently.

2.4 Authentication bypass and remote code execution

The first part of the chain enables the attacker to bypass the expected authentication process.

The attacker can then reach functionality that would normally require authentication and use the vulnerable application components to execute commands.

The resulting execution initially occurs with the privileges of the appliance's web server user.

The remaining vulnerabilities allow the attacker to progress from this initial execution context toward root-level privileges.

2.5 File upload and predictable identifiers

CVE-2026-118527 affects how predictable identifiers are generated.

An attacker can exploit this weakness to upload content to a known location on the appliance's disk.

In the reported chain, this file-handling weakness contributes to remote code execution when combined with the authentication bypass.

The vulnerability illustrates how predictable file locations and insufficient validation can become more dangerous when combined with other weaknesses in the same product.

2.6 Privilege escalation to root

The final stage involves CVE-2026-111357.

The vulnerability affects a critical function and allows privilege escalation under the conditions described in the advisory.

Volexity reported that the attacker used this stage to obtain root-level command execution.

Root access provides extensive control over the appliance and can expose sensitive information stored on the system or accessible through its configured services.

3. Attack Overview

3.1 Threat actor: UTA0576

The exploitation activity was attributed by Volexity to a previously undocumented threat actor tracked as UTA0576.

The actor was observed chaining the three Ivanti Connect Secure vulnerabilities to obtain unauthenticated root-level access.

Rather than focusing primarily on deploying traditional malware or web shells, the observed activity concentrated on credential collection, reconnaissance, and discovery of sensitive organizational information.

The available reporting does not establish the actor's definitive identity or broader organizational affiliation.

3.2 Attack sequence

The observed attack can be summarized as follows:

  1. Target identification: The attacker identifies an exposed Ivanti Connect Secure appliance.

  2. Authentication bypass: CVE-2026-104935 is exploited to bypass normal authentication controls.

  3. Remote code execution: The attacker obtains an initial command-execution capability on the appliance.

  4. File upload: CVE-2026-118527 is used as part of the file-handling and execution chain.

  5. Privilege escalation: CVE-2026-111357 is exploited to elevate privileges.

  6. Root-level access: The attacker obtains unauthenticated root-level command execution.

  7. Credential collection: Stored credentials, including LDAP domain credentials, are extracted.

  8. Active Directory reconnaissance: The attacker searches directory information for administrator passwords and BitLocker recovery keys.

  9. Additional discovery: Host reconnaissance and password-spraying activity are conducted.

This sequence represents the reported exploit chain and observed post-exploitation behavior.

3.3 Timeline of key developments

DateEvent
July 2026Ivanti reported that it had identified and patched a portion of the relevant vulnerability in release 25.1.3.0, while working to backport the fix to other supported versions.
October 3, 2026Volexity observed the beginning of exploitation against a customer appliance.
October 13, 2026Volexity publicly documented the three-vulnerability exploit chain and identified the threat actor as UTA0576.
October 13, 2026CISA added CVE-2026-104935 to its KEV catalog.
October 2026Ivanti initially prioritized releasing a fix for the primary authentication-bypass exploitation path while work continued on the privilege-escalation fix.
October 30, 2026CISA added CVE-2026-111357 and CVE-2026-118527 to its KEV catalog.
October 31, 2026The Hacker News reported that fixes for all three vulnerabilities were available in the latest applicable Ivanti Connect Secure releases.

3.4 Observed post-exploitation activities

After obtaining access, UTA0576 was observed performing activities focused on gathering authentication material and understanding the internal environment.

These included:

  • Extracting credentials stored on the VPN appliance.

  • Collecting LDAP domain credentials.

  • Gathering limited Active Directory metadata.

  • Conducting host reconnaissance.

  • Searching for administrator passwords.

  • Searching for BitLocker recovery keys.

  • Performing password-spraying activity.

The activity suggests that the appliance was used as a valuable source of internal identity and infrastructure information.

The report does not describe a confirmed ransomware deployment or a traditional persistent web-shell installation as part of the observed activity.

4. Technical Analysis

4.1 Exploitation of a fully patched appliance

One of the most important findings from Volexity's investigation was that the targeted Ivanti Connect Secure appliance was running version 22.8R2.4 and was fully patched at the time of the initial discovery.

This demonstrates that being fully updated according to the patches available at a particular time does not guarantee protection against previously unknown vulnerabilities.

The attack involved vulnerabilities that were not yet fully addressed through available fixes when exploitation was discovered.

Organizations should therefore combine patch management with continuous monitoring, vulnerability intelligence, and appliance-level forensic investigation.

4.2 Credential extraction

Following exploitation, UTA0576 focused on extracting credentials stored on the Ivanti appliance.

The collected information included LDAP domain credentials used by the VPN to interact with directory services.

Such credentials can be valuable because they may provide access to internal authentication infrastructure and help an attacker understand the organization's identity environment.

The exposure of these credentials can also create risks beyond the compromised VPN appliance if the accounts have permissions across other internal systems.

4.3 Active Directory reconnaissance

The attacker used information available through the compromised environment to investigate Active Directory.

The observed activity included searching for:

  • Administrator passwords.

  • Local Administrator Password Solution (LAPS) passwords.

  • BitLocker recovery keys.

  • Directory-related authentication attributes.

  • Other sensitive account information.

LAPS is used to manage local administrator passwords across Windows systems, while BitLocker recovery keys can be used to recover encrypted drives.

Unauthorized access to these items can significantly increase the impact of an enterprise identity compromise.

4.4 Password-spraying activity

Volexity observed UTA0576 conducting password-spraying attacks against Active Directory accounts.

Password spraying involves attempting a limited number of commonly used or selected passwords across multiple accounts rather than repeatedly trying many passwords against one account.

This approach can be used to identify accounts with weak or reused credentials while attempting to avoid account lockout thresholds.

Organizations should monitor authentication logs for repeated failed login attempts across multiple accounts, especially when the attempts originate from VPN infrastructure or unusual internal sources.

4.5 Host reconnaissance

The attacker also conducted host reconnaissance to understand the compromised environment.

Reconnaissance can help identify:

  • Available internal systems.

  • Network relationships.

  • Authentication services.

  • Domain infrastructure.

  • Privileged accounts.

  • Potentially valuable systems and information.

The observed reconnaissance activity indicates that the attacker was interested in understanding the environment and collecting information that could support further access.

4.6 Why no web shell or backdoor was required

A notable aspect of this activity is that Volexity did not observe the attacker leaving a traditional web shell or persistent backdoor.

Instead, the attacker reportedly reran the complete exploit chain for each command.

This approach reduces the need to maintain a separate malicious implant on the appliance.

It also creates forensic challenges because investigators cannot rely exclusively on searching for familiar web-shell files or persistent malware.

The absence of a backdoor does not mean that the device was not compromised. Attackers may execute commands through vulnerable application functionality while attempting to minimize changes to the filesystem.

4.7 Forensic visibility and integrity-check limitations

The exploit chain included actions designed to make forensic detection more difficult.

Volexity reported that the attacker modified library code in memory and restored configuration data that had been altered.

The attacker also took steps to avoid detection by Ivanti's Integrity Checker Tool.

Consequently, the tool may not identify this particular exploitation activity.

This is an important distinction for incident responders: a clean integrity-check result should not be treated as definitive proof that an appliance has never been compromised.

A suspected compromise requires a broader investigation that may include network and memory forensics, authentication records, appliance logs, and other available evidence.

4.8 Ivanti's patching response

Ivanti initially focused on releasing a fix for CVE-2026-104935, which addressed the primary exploitation path.

At the time exploitation was discovered, the company was still working on the fix for the local privilege-escalation vulnerability.

Ivanti explained that it chose to release the primary fix without delaying customer protection while the remaining work continued.

The company subsequently released updates addressing CVE-2026-111357 and CVE-2026-118527.

According to The Hacker News, the latest applicable releases address all three vulnerabilities involved in the observed exploit chain.

4.9 Why patching only the first vulnerability is insufficient

The exploit chain demonstrates that fixing the initial authentication-bypass weakness does not automatically address every vulnerability involved.

Organizations that installed an earlier update addressing only CVE-2026-104935 may still need to apply the subsequent updates for their particular software branch.

The final remediation must address all three vulnerabilities.

Organizations should verify the installed version against Ivanti's current advisory rather than assuming that an earlier security update provides complete protection.

5. Potential Impact

5.1 Unauthorized root-level access

Successful exploitation can allow an unauthenticated attacker to execute commands with root privileges on an affected Ivanti Connect Secure appliance.

This provides extensive control over the compromised VPN gateway.

5.2 Credential exposure

The attacker may extract credentials stored on the appliance, including LDAP domain credentials.

Exposed credentials may be used to access additional organizational resources if they remain valid.

5.3 Active Directory compromise

Access to directory metadata, administrator passwords, LAPS credentials, and other sensitive authentication information may provide opportunities for further compromise of Windows environments.

5.4 BitLocker recovery-key exposure

BitLocker recovery keys can be used to recover encrypted Windows drives.

Unauthorized access to these keys can weaken the confidentiality protections provided by full-disk encryption, depending on the circumstances and associated access to the systems.

5.5 Privileged account compromise

The discovery of administrator credentials and other authentication material can increase the risk of unauthorized access to privileged systems and services.

5.6 Lateral movement

Compromised VPN credentials and Active Directory information may help an attacker identify additional internal systems and authentication paths.

The available reporting confirms reconnaissance and password spraying but does not establish that every observed victim experienced successful lateral movement.

5.7 Reduced forensic visibility

Memory-only changes, restored configuration data, and selective evidence removal can make traditional integrity checks less reliable.

Organizations may underestimate the extent of compromise if they rely on a single integrity-checking mechanism.

5.8 Enterprise network exposure

Because Ivanti Connect Secure provides remote access to internal resources, compromise of the appliance can expose sensitive organizational authentication and network information.

The ultimate impact depends on the appliance's configuration, connected identity services, account privileges, and the extent of additional access obtained.

6. Recommendations

6.1 Immediate Actions

1. Upgrade affected Ivanti Connect Secure appliances

Install the appropriate fixed version for the affected software branch.

The versions reported by The Hacker News are:

  • 25.1.1.2 and earlier: upgrade to 25.1.1.3.

  • 22.8R2.5 and earlier: upgrade to 22.8R2.6.

Organizations should consult Ivanti's latest security advisory to verify the correct fixed release for their exact branch.

2. Confirm that all three vulnerabilities are addressed

Do not assume that installing the earlier CVE-2026-104935 fix resolves the entire exploit chain.

Verify that the installed version also addresses:

  • CVE-2026-104935.

  • CVE-2026-118527.

  • CVE-2026-111357.

3. Investigate potential exploitation

Review VPN appliance logs, network telemetry, authentication activity, and other available forensic records for suspicious behavior.

A successful patch installation does not establish that the appliance was never compromised.

4. Review stored credentials

Identify credentials stored or configured on the appliance, including LDAP and domain service-account credentials.

If compromise is suspected, rotate exposed credentials from a trusted environment.

5. Review Active Directory activity

Investigate suspicious access to administrator passwords, LAPS credentials, BitLocker recovery keys, and sensitive directory attributes.

6. Monitor password-spraying attempts

Review authentication records for repeated failed login attempts across multiple accounts.

Pay particular attention to activity originating from VPN appliances or unexpected internal network locations.

7. Review privileged account activity

Investigate unexpected administrative access, unusual account authentication, and suspicious use of privileged identities.

8. Preserve forensic evidence

Retain relevant appliance logs, network traffic, authentication records, and available memory evidence.

Do not rely exclusively on the Ivanti Integrity Checker Tool to determine whether a compromise occurred.

9. Apply CISA KEV requirements

Federal Civilian Executive Branch agencies should meet the reported remediation deadlines:

  • CVE-2026-111357: November 2, 2026.

  • CVE-2026-118527: November 13, 2026.

Other organizations should prioritize remediation based on their exposure and risk.

6.2 Preventive Actions

1. Maintain an updated VPN appliance inventory

Record all Ivanti Connect Secure appliances, software versions, deployment locations, and administrative owners.

2. Establish an emergency patching process

Treat vulnerabilities in internet-facing VPN appliances as high-priority risks, particularly when active exploitation has been confirmed.

3. Protect LDAP and domain credentials

Use dedicated service accounts with restricted permissions. Avoid unnecessary privilege assignments and rotate credentials when exposure is suspected.

4. Strengthen Active Directory monitoring

Monitor privileged account access, LAPS password retrieval, sensitive directory attributes, and unusual authentication patterns.

5. Monitor password-spraying behavior

Deploy authentication monitoring that identifies repeated login failures across multiple accounts and detects suspicious activity originating from VPN infrastructure.

6. Secure BitLocker recovery information

Restrict access to recovery keys and monitor retrieval activity. Ensure that recovery information is available only to authorized administrators and services.

7. Improve appliance logging

Centralize available VPN appliance logs and correlate them with identity, network, and endpoint telemetry.

8. Perform forensic investigations after suspected compromise

Do not treat patching or a successful integrity check as sufficient proof of recovery. Investigate historical activity and determine whether credentials or internal systems were exposed.

9. Restrict administrative access

Limit access to VPN appliance management interfaces to authorized administrative systems and networks.

10. Review third-party security advisories

Monitor Ivanti, CISA, and trusted vulnerability-research organizations for updates concerning exploited vulnerabilities and additional remediation guidance.

7. Detection and Threat-Hunting Guidance

Security teams should investigate Ivanti Connect Secure appliances using network, application, authentication, and forensic evidence.

7.1 Detection matrix

Detection areaInvestigation focus
VPN web requestsUnusual requests to authentication-related endpoints.
HTTP headersUnexpected discrepancies between URL paths and X-DSCGI-PATH header values.
File activityUnexpected files or temporary artifacts created on the appliance.
Appliance processesUnusual processes or commands executed by VPN services.
Authentication logsRepeated failed logins and suspicious password-spraying activity.
LDAP activityUnusual authentication requests or access involving domain service accounts.
Active DirectorySuspicious queries for administrator passwords and sensitive directory attributes.
LAPS accessUnexpected retrieval of local administrator passwords.
BitLocker recoveryUnusual access to recovery-key information.
Network activityUnexpected connections between the VPN appliance and internal systems.
Privilege changesUnusual execution or administrative activity involving the appliance.
Forensic integrityEvidence of log gaps, unexplained changes, or suspicious memory activity.

7.2 Exploitation-related investigation

Volexity documented suspicious requests involving the following authentication-related URL path:

/dana-na/auth/url_default/welcome.cgi

The investigation also identified requests containing an X-DSCGI-PATH header whose value did not match the requested URL path.

Security teams should review such discrepancies in the context of the reported exploit chain and correlate them with application logs, network traffic, and other forensic evidence.

7.3 Credential and identity threat hunting

Investigate:

  • Unexpected LDAP authentication activity.

  • Access to domain administrator credentials.

  • LAPS password retrieval.

  • BitLocker recovery-key access.

  • Suspicious Active Directory queries.

  • Password spraying against multiple accounts.

  • Unusual VPN authentication and session activity.

The objective is to determine whether the VPN appliance was used to collect authentication material and whether any exposed credentials were subsequently used elsewhere.

7.4 Forensic investigation considerations

Because the attacker reportedly modified information in memory and restored configuration data, traditional integrity checks may not reveal all evidence of exploitation.

Investigators should consider:

  • Network forensics.

  • Memory forensics.

  • VPN application logs.

  • Authentication and directory-service logs.

  • Internal network traffic.

  • Available appliance filesystem evidence.

  • Evidence of log truncation or unexplained gaps.

A clean result from an integrity-checking tool should not be considered conclusive evidence that an appliance is uncompromised.

8. Conclusion

The exploitation of three Ivanti Connect Secure vulnerabilities demonstrates how attackers can combine multiple security weaknesses to achieve a much more serious outcome than any individual vulnerability may suggest.

By chaining CVE-2026-104935, CVE-2026-118527, and CVE-2026-111357, the threat actor UTA0576 was able to obtain unauthenticated root-level access to vulnerable VPN appliances.

The observed post-exploitation activity focused on credential extraction, Active Directory reconnaissance, administrator-password discovery, BitLocker recovery-key collection, and password spraying.

The absence of a traditional web shell or persistent backdoor makes the activity particularly important from a forensic perspective. Attackers reportedly reran the exploit chain for individual commands, while memory modifications and restored configuration data complicated detection through conventional integrity checks.

CISA's addition of the remaining two vulnerabilities to its KEV catalog on October 30, 2026, reinforces the urgency of addressing the complete exploit chain.

Organizations should upgrade affected appliances to the appropriate fixed releases, rotate potentially exposed credentials, investigate Active Directory activity, and conduct forensic assessments where compromise is suspected.

The central lesson is that patching the initial vulnerability is not enough when an attacker can chain additional weaknesses to achieve full system control. Organizations must validate complete remediation and investigate whether sensitive credentials and internal identity infrastructure were exposed.

MITRE ATT&CK Mapping

T1190 — Exploit Public-Facing ApplicationT1068 — Exploitation for Privilege EscalationT1110.003 — Password SprayingT1087.002 — Domain Account DiscoveryT1018 — Remote System Discovery