CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Ivanti Connect Secure: generation of predictable numbers or identifiers lets a remote authenticated attacker upload files with attacker-controlled content to a known location on disk, chainable with CVE-2026-104935 and CVE-2026-111357; CISA KEV 2026-10-30, no public CVE record or fixed build yet

cve · CVE-2026-118527

Coverage
1
first 2026-10-14 → last 2026-10-31
Latest activity
2026-10-31
Ivanti Connect Secure chain: root step patched 29 Oct, CISA lists three flaws; 25.1.1.2 and 22.8R2.5 fall…
Peak priority
critical
1 critical
Targets
technology
sectors: technology
Sources cited
10
8 hosts

Action items (3)

Do-now tasks recorded on the entries about CVE-2026-118527, newest first. Check the date before acting on an older one.

  • Immediate action: Ivanti and CISA confirm exploitation of CVE-2026-104935, and Volexity saw the chain used against a fully patched 22.8R2.4 appliance from 2026-10-03. Upgrade every Connect Secure appliance to 25.1.1.3, 25.1.3.1 or 22.8R2.6, internet-facing ones first: after Ivanti patched the root-escalation step on 2026-10-29 the Canadian Cyber Centre lists every earlier build as affected, 25.1.1.2 and 22.8R2.5 included. Ivanti's Integrity Checker Tool cannot see this chain, so an appliance that was reachable on an affected build needs a compromise check and rotation of the Active Directory service account, LAPS passwords and other secrets it could reach.
    2026-10-14CVE-2026-104935 +2
  • Upgrade every Ivanti Connect Secure appliance to 25.1.1.3, 25.1.3.1 or 22.8R2.6 now, internet-facing appliances first: the Canadian Cyber Centre lists every earlier build as affected, so appliances that took only the 2026-10-13 builds 25.1.1.2 or 22.8R2.5 are still short of the root-step patch; 22.7.x and below are not affected.
    2026-10-14CVE-2026-104935 +2
  • Run a compromise check on every appliance that was reachable on an affected build, starting with proxy, load balancer or WAF logs back to at least 2026-10-03 for welcome.cgi requests that carry an X-DSCGI-PATH header; where compromise cannot be excluded, first cut the appliance off from the internet and the internal network and snapshot a virtual appliance's file system and memory without powering it down, then follow Ivanti's recovery steps and reset the domain service account, LAPS and local passwords, certificates, API keys, the Kerberos tickets of its service accounts and the licence-server authentication the appliance held, because CERT-FR knows of lateral movement using the LDAP and Active Directory secrets.
    2026-10-14CVE-2026-104935 +2

Defender insights

What each entry about CVE-2026-118527 tells a defender to do, newest first.

2026-10-14CRITICALexploitedIvanti Connect Secure chain: root step patched 29 Oct, CISA lists three flaws; 25.1.1.2 and 22.8R2.5 fall short

Exposure · detection

Story timeline

  1. 2026-10-14CVE-2026-104935, Ivanti Connect Secure: an authentication bypass chained to code execution is exploited as a zero-day, the root-escalation step was patched on 2026-10-29 and CISA lists all three chain flaws (CVSS 8.6)
    trending-vulnerabilitiesIvanti Connect Secure chain: root step patched 29 Oct, CISA lists three flaws; 25.1.1.2 and 22.8R2.5 fall short
ATT&CK techniques (9 across 8 tactics)

9 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application
  • ExecutionCommand and Scripting Interpreter: Python
  • Privilege EscalationExploitation for Privilege Escalation
  • Defense ImpairmentDisable or Modify Tools: Clear Linux or Mac System Logs
  • Credential AccessNetwork Sniffing · Brute Force: Password Spraying
  • DiscoveryNetwork Sniffing · Account Discovery: Domain Account
  • Command and ControlApplication Layer Protocol: Web Protocols
  • ExfiltrationExfiltration Over C2 Channel

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

Execution TA0002

T1059.006Command and Scripting Interpreter: Python×1

Adversaries may abuse Python commands and scripts for execution. Python is a very popular scripting/programming language, with capabilities to perform many functions. Python can be executed interactively from the command-line (via the <code>python.exe</code> interpreter) or via scripts (.py) that can be written and distributed to different systems. Python code can also be compiled into binary executables.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

Privilege Escalation TA0004

T1068Exploitation for Privilege Escalation×1

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

Defense Impairment TA0112

T1685.006Disable or Modify Tools: Clear Linux or Mac System Logs×1

Adversaries may clear system logs to hide evidence of an intrusion. macOS and Linux both keep track of system or user-initiated actions via system logs. The majority of native system logging is stored under the `/var/log/` directory. Subfolders in this directory categorize logs by their related functions, such as:

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

Credential Access TA0006

T1040Network Sniffing×1

Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network. Network sniffing refers to using the network interface on a system to monitor or capture information sent over a wired or wireless connection. An adversary may place a network interface into promiscuous mode to passively access data in transit over the network, or use span ports to capture a larger amount of data.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

T1110.003Brute Force: Password Spraying×1

Adversaries may use a single or small list of commonly used passwords against many different accounts to attempt to acquire valid account credentials. Password spraying uses one password (e.g. 'Password01'), or a small list of commonly used passwords, that may match the complexity policy of the domain. Logins are attempted with that password against many different accounts on a network to avoid account lockouts that would normally occur when brute forcing a single account with many passwords.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

Discovery TA0007

T1040Network Sniffing×1

Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network. Network sniffing refers to using the network interface on a system to monitor or capture information sent over a wired or wireless connection. An adversary may place a network interface into promiscuous mode to passively access data in transit over the network, or use span ports to capture a larger amount of data.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

T1087.002Account Discovery: Domain Account×1

Adversaries may attempt to get a listing of domain accounts. This information can help adversaries determine which domain accounts exist to aid in follow-on behavior such as targeting specific accounts which possess particular privileges.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

Command and Control TA0011

T1071.001Application Layer Protocol: Web Protocols×1

Adversaries may communicate using application layer protocols associated with web traffic to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

Exfiltration TA0010

T1041Exfiltration Over C2 Channel×1

Adversaries may steal data by exfiltrating it over an existing command and control channel. Stolen data is encoded into the normal communications channel using the same protocol as command and control communications.

Evidence: 2026-10-14/cve-2026-104935-ivanti-connect-secure-zero-day-chain-kev · ATT&CK page ↗

Entries about Ivanti Connect Secure: generation of predictable numbers or identifiers lets a remote authenticated attacker upload files with attacker-controlled content to a known location on disk, chainable with CVE-2026-104935 and CVE-2026-111357; CISA KEV 2026-10-30, no public CVE record or fixed build yet (1)

2026-10-14 · view entry permalink →

CRITICALCVE-2026-104935 +2exploitedupdatedNATOA1

CVE-2026-104935, Ivanti Connect Secure: an authentication bypass chained to code execution is exploited as a zero-day, the root-escalation step was patched on 2026-10-29 and CISA lists all three chain flaws (CVSS 8.6)

Ivanti disclosed CVE-2026-104935 in Connect Secure on 2026-10-13 and says it is aware of limited exploitation in the wild (Ivanti, 2026-10-13); Rapid7 describes it as an authentication bypass by spoofing that lets a remote unauthenticated attacker run commands, CVSS 8.6 (Rapid7, 2026-10-13), and CISA listed it in KEV the same day (CISA, 2026-10-13). Volexity tracks the operator as UTA0576 and dates exploitation of a fully patched 22.8R2.4 appliance to 2026-10-03 (Volexity, 2026-10-13).

The chain has three steps. A request to the public login script welcome.cgi names a protected script in an X-DSCGI-PATH header, so the URL passes the authentication check and the header picks the destination. The upload script wu.cgi writes a file to disk before checking that it is a ZIP, and parallel requests run a Perl script before it is deleted. A root escalation then abuses the dsinvoked service's trust in the shared DSCache configuration store (Volexity, 2026-10-13). The first two steps are CVE-2026-104935 and the root step is CVE-2026-111357 (GitHub Advisory Database, 2026-10-15); Volexity's update banner says Ivanti patched it on 2026-10-29 (Volexity, 2026-10-13). CISA listed it and a third chain flaw, CVE-2026-118527, on 2026-10-30, says each can be chained with the other two, and describes CVE-2026-118527 as a predictable-identifier flaw that lets a remote authenticated attacker upload files with attacker-controlled content to a known location on disk (CISA KEV catalog, 2026-10-30). No source says which step of the chain that is, and it has no public CVE record or fixed build yet.

The exploit leaves no web shell and patches library code in memory only, so Ivanti's Integrity Checker Tool, which looks for file changes, does not detect it, and Volexity found log entries removed. The operator then went after the Active Directory service account stored on the appliance: LDAP queries for LAPS passwords, BitLocker recovery keys and password attributes, password spraying, and packet capture of plaintext LDAP, HTTP Basic and NTLM traffic (Volexity, 2026-10-13).

At the time of disclosure, Ivanti is aware of limited exploitation in the wild.

Ivanti 2026-10-13

In the first week of October 2026, Volexity 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.

because this exploit chain patches library code in memory only and restores configuration store data, the tool does not detect any modifications.

Volexity 2026-10-13

apply the appropriate update on an emergency basis outside of normal patching cycles

Rapid7 2026-10-13

CERT-FR is aware of lateral movement using these secrets.

ANSSI / CERT-FR

Ivanti Connect Secure 22.8R2.4 mishandles the manner in which the dsinvoked broker trusts DSCache configuration data, leading to privilege escalation to root, as exploited in the wild in October 2026.

GitHub Advisory Database 2026-10-15

Open-source reporting indicates that CVE-2026-111357 is being exploited in the wild.

Canadian Centre for Cyber Security 2026-10-13

Authentication bypass by spoofing in ICS before version 25.1.3.0 allows a remote unauthenticated attacker to execute arbitrary commands.

Ivanti, via ENISA EUVD (EUVD-2026-98816)

On October 29, 2026, Ivanti published a patch that addresses this vulnerability, which is tracked as CVE-2026-111357.

Volexity 2026-10-13

Ivanti Connect Secure contains a generation of predictable numbers or identifiers vulnerability that allows a remote authenticated attacker to upload files with attacker-controlled content to a known location on disk.

This vulnerability can be chained with CVE-2026-104935 and CVE-2026-111357.

CISA KEV catalog 2026-10-30

On October 30, 2026, Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-111357 and CVE-2026-118527 to their Known Exploited Vulnerabilities (KEV) Catalog.

Canadian Centre for Cyber Security 2026-10-13
Updaterun 2026-10-16T0256Z-intelsummaryimmediate_actioncvessourcesevidencesourcing_noteactionsbody

CERT-FR's alert of 2026-10-14 says Ivanti reports the vulnerability as actively exploited and that CERT-FR itself is aware of lateral movement using the LDAP and Active Directory secrets stored on the appliance (CERT-FR, 2026-10-14). It puts the response in an order: fully isolate the appliance from both the internet and the internal network, snapshot the file system and memory of a virtual appliance, avoid powering it off so that traces survive, place the logs under seal and analyse the appliance with the Volexity indicators, and only then, on compromise, factory-reset it, upgrade and reset the secrets (CERT-FR, 2026-10-14). Its list of secrets to treat as compromised is wider than a password reset: the LDAP and Active Directory secrets, every certificate on the appliance (machine, user-authentication, code-signing and the TLS certificate of the exposed interface), the administration password, stored API keys, the passwords of local accounts including the service accounts used for authentication servers, the Kerberos tickets and other authentication material of those service accounts, and the licence-server authentication (CERT-FR, 2026-10-14). CERT-FR adds that running Ivanti's external Integrity Checker Tool needs physical access to the appliance and can interrupt service, and that some threats survive a factory reset (CERT-FR, 2026-10-14). Its affected-systems list names the 22.8Rx builds before 22.8R2.5, the 25.1.1.x builds before 25.1.1.2 and the 25.1.3.x builds before 25.1.3.1 and does not list a 25.1.2.x line; by counting 25.1.3.x builds before 25.1.3.1 as affected it includes 25.1.3.0, a build that Rapid7's table lists as resolved (CERT-FR, 2026-10-14).

Improvementrun 2026-10-17T0256Z-inteltitleheadlinesummaryimmediate_actioncvessourcesevidencebody

The root-escalation step of the chain now has its own identifier, CVE-2026-111357, published on 2026-10-15 and rated High on GitHub's advisory database as GHSA-fhw5-mpvj-x89m (GitHub Advisory Database, 2026-10-15). Its description reads "Ivanti Connect Secure 22.8R2.4 mishandles the manner in which the dsinvoked broker trusts DSCache configuration data, leading to privilege escalation to root, as exploited in the wild in October 2026." (GitHub Advisory Database, 2026-10-15), the same step Volexity describes as abusing the dsinvoked service's trust in the shared DSCache store (Volexity, 2026-10-13).

The record names only 22.8R2.4 as affected and states no fixed build; Volexity wrote that Ivanti was working on a fix for release in the coming weeks (Volexity, 2026-10-13), and no source read says whether any build now fixes it. The Canadian Cyber Centre's bulletin on the Ivanti advisory, updated 2026-10-16, adds that open-source reporting indicates CVE-2026-111357 is being exploited in the wild (Canadian Centre for Cyber Security, 2026-10-13). A scanner, SIEM enrichment rule or ticket can now follow the unfixed step by this ID, and an appliance that was exposed still needs the compromise check above.

Improvementrun 2026-10-21T0800Z-auditbodyevidencesourcessourcing_notesummary

Ivanti's own description of CVE-2026-104935, as the numbering authority, reads "Authentication bypass by spoofing in ICS before version 25.1.3.0 allows a remote unauthenticated attacker to execute arbitrary commands" (ENISA EUVD, 2026-10-13). Rapid7 relays that, according to Ivanti, a portion of the flaw was found through its product security program and patched in the July 2026 release of 25.1.3.0, and that exploitation occurred while Ivanti was backporting the fix to the other supported versions (Rapid7, 2026-10-13). CERT-FR still lists 25.1.3.x builds before 25.1.3.1 as affected (CERT-FR, 2026-10-14), so 25.1.3.1 remains the build to reach on that line.

Updaterun 2026-10-31T0256Z-inteltitleheadlinesummaryimmediate_actioncvessourcesevidencesourcing_noteactionsbody

Volexity's report now carries an update banner saying Ivanti published a patch on 2026-10-29 for the privilege-escalation step, which is tracked as CVE-2026-111357 (Volexity, 2026-10-13). CISA added CVE-2026-111357 and a third chain flaw, CVE-2026-118527, to its Known Exploited Vulnerabilities catalog on 2026-10-30 (CISA, 2026-10-30). The catalog describes CVE-2026-118527 as a generation-of-predictable-numbers-or-identifiers flaw that lets a remote authenticated attacker upload files with attacker-controlled content to a known location on disk, and says it can be chained with CVE-2026-104935 and CVE-2026-111357 (CISA KEV catalog, 2026-10-30). The Canadian Cyber Centre's bulletin on Ivanti's advisory, updated 2026-10-30, now lists the Connect Secure versions before 25.1.1.3, 25.1.3.1 and 22.8R2.6 as affected (Canadian Centre for Cyber Security, 2026-10-13), a range that takes in 25.1.1.2 and 22.8R2.5, the builds of 2026-10-13; CISA's alert, updated the same day, lists versions 25.1.1.2 and prior, 25.1.2.2 and prior and 22.8R2.5 and prior as affected by the three chain CVEs (CISA, 2026-10-13). Ivanti's advisory page could not be read, so which build carries which CVE's fix is not confirmed, and CVE-2026-118527 has no public CVE record, affected range or fixed build yet.

vulnerability14 Oct 03:38Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • cisa.gov3 (30%)
  • cert.ssi.gouv.fr1 (10%)
  • cyber.gc.ca1 (10%)
  • euvd.enisa.europa.eu1 (10%)
  • github.com1 (10%)
  • ivanti.com1 (10%)
  • rapid7.com1 (10%)
  • volexity.com1 (10%)

External references

NVD · cve.org · CISA KEV

All cited sources (10)