Ivanti Connect Secure CVE-2026-111357 and CVE-2026-118527: update your VPN gateway now

Venus Yazılım5 min read

Chainable Ivanti Connect Secure flaws are being exploited to gain root. Upgrade your VPN appliance to the latest release and check it for compromise.

If your remote staff connect to the company network with Ivanti Connect Secure, this VPN appliance is one of the first places attackers look. This article covers two flaws being exploited in the wild and how to check your appliance.

Short answer: CVE-2026-111357 and CVE-2026-118527 are parts of a chain that Volexity reported, which starts with CVE-2026-104935. The chain begins with an unauthenticated event and can reach root. CISA added both flaws to the KEV catalog on October 30, 2026. If you run Ivanti Connect Secure, upgrade to the latest release and run the Integrity Checker Tool, knowing that it has limits for this chain.

At a glance

Field CVE-2026-111357 CVE-2026-118527
CVSS 7.0, High (v3.1, NVD) 4.3, Medium (v3.1, NVD)
Flaw type Missing authentication for a critical function, escalation to root Predictable file names, arbitrary file write
Authentication Local access and a user account required (AV:L, PR:L) Authenticated remote attacker required (AV:N, PR:L)
Active exploitation Yes. NVD says it was exploited in October 2026 Yes. The KEV record shows active exploitation
CISA KEV added October 30, 2026 October 30, 2026
Fixed version NVD lists no fixed version; upgrade to the latest release 25.1.1.3 and 22.8R2.6 (NVD)

CVSS scores come from the NVD records. Neither NVD record includes a CVSS v4.0 score.

What happened?

According to Volexity, exploitation began on October 3, 2026. The attacker used the chain in three steps. First, an authentication bypass let requests reach a protected CGI handler. Second, a file-write flaw led to code execution as the CGI server user. Third, a privilege escalation flaw gave root access. Volexity tracks this activity as UTA0576 and says confidence in any criminal motive is low.

The patches came in two stages. Volexity reports that the authentication bypass and remote code execution fixes were released on October 13, 2026, and the privilege escalation fix on October 29, 2026. NVD describes CVE-2026-111357 as a privilege escalation to root in Connect Secure 22.8R2.4, caused by the dsinvoked broker trusting DSCache configuration data.

CVE-2026-118527 comes from predictable file names in Connect Secure. It allows a remote attacker with valid credentials to upload files with attacker-controlled content to a known location on disk. In the chain, this corresponds to the file-write step.

Who is affected?

  • NVD for CVE-2026-118527 lists versions from 25.1.0.0 up to, but not including, 25.1.1.3, and versions from 22.8R2 through 22.8R2.5 as affected. It marks 25.1.1.3 and 22.8R2.6 as unaffected.
  • NVD for CVE-2026-111357 lists only 22.8R2.4.
  • Volexity advises upgrading installations on 25.1.1 and earlier, 25.1.2, and 22.8R2.4 to the newest release.

NVD does not list a separate fixed version for CVE-2026-111357. Ivanti’s advisory is the authoritative list of fixed releases; compare your appliance version with it before and after upgrading.

What should you do?

  1. Check your appliance version. The sources do not give a command for this. Open the version information in the Ivanti administration console and compare it with the lists above.
  2. Upgrade to the latest release. NVD gives 25.1.1.3 and 22.8R2.6 as the fixed versions for CVE-2026-118527. For CVE-2026-111357, Volexity recommends moving to the newest release.
  3. Run the Ivanti Integrity Checker Tool (ICT). Volexity notes that ICT does not detect the changes made in this chain. A clean ICT result does not prove that the appliance is clean.
  4. If you cannot upgrade right away, the sources list no official temporary mitigation. Volexity suggests monitoring. Watch for sudden spikes in requests to welcome.cgi, and for requests where the X-DSCGI-PATH header does not match the URL path. This is a detection step, not a fix.
  5. After patching, Volexity recommends network and memory forensics on any appliance you suspect was compromised.

Have I been hit?

The indicators below come from the Volexity report. The report gives no file hashes and names no standalone malware or web shell. It also lists network indicators, including an IP address, which we have left out. Check the original report for those.

  • Temporary scripts in /tmp/: ml.py, rq5.py, mk.py, rr.py, sp_run.py. Output files: pu.txt, sp_out.txt, spray_hits.json.
  • The /data/.icscap/ directory, with h.py, dsstatmond (a renamed tcpdump), and cap* files.
  • Files matching ics-root-run-inband-*.pl and ics-root-result-inband-* under /home/runtime/tmp/.
  • Tampering with log files such as /var/log/audit/audit.log and /home/runtime/dlogs/debuglog.
  • Requests to /dana-na/auth/url_default/welcome.cgi where the X-DSCGI-PATH header does not match the URL path.

If you have shell access to the appliance, search /tmp/ and /data/.icscap/ for the names above. If you do not, ask Ivanti support to run this check. Volexity says the attacker made in-memory changes, so a file search alone may not be enough.

Frequently asked questions

I have no local user accounts. Am I safe?

We cannot say that. CVE-2026-111357 requires local access and an account, but the chain Volexity describes begins with unauthenticated events.

If ICT reports no changes, am I safe?

No. Volexity says ICT does not detect the modifications from this chain. Those changes happened in memory and in configuration data.

After patching, is there anything else to do?

If you suspect the appliance was compromised, run the network and memory forensics Volexity recommends. The patch alone does not answer that question.

If you want help tracking patches for VPN and network appliances, take a look at our server management service.

Sources

More notes

  1. 4 min read

    Google Brotli CVE-2026-111497: memory overflow in Node.js and Brotli libraries

    A memory overflow in the Brotli decoder (CVE-2026-111497) can lead to code execution without logging in. Update Node.js and Brotli.

  2. 5 min read

    Cisco ASA and FTD CVE-2026-76418: SSL VPN reload flaw and fixed releases

    Unauthenticated attackers can reload Cisco ASA and FTD devices through SSL VPN when secondary authentication is set. It is being exploited. Check and upgrade.

Let’s reserve a slot in the rack.

Describe your project in a few steps and we’ll prepare a written proposal with scope, timeline and an infrastructure plan.

Request a quoteor write directly: email address