Skip to content
Blog

Ivanti · Ivanti Connect Secure · VPN

Ivanti Connect Secure CVE-2026-118527: The NVD Entry for the Third Link in the KEV Chain

CVE-2026-118527: predictable filenames in Ivanti Connect Secure, in CISA KEV since October 30, NVD entry published November 3. Scored 4.3, version bounds.

4 min readCVE-2026-118527

On October 30, 2026, CISA added two Ivanti Connect Secure vulnerabilities to its KEV catalog. The first, CVE-2026-111357, was covered in our October 31 article. The second had no NVD entry at the time, so we described it from CISA's text alone.

That entry went live on November 3: it is CVE-2026-118527. NVD has already analyzed it, with precise version bounds. And the score is a surprise: 4.3, MEDIUM.

FieldValue
CVECVE-2026-118527
CVSS 3.1 (CNA, secondary score)4.3 (MEDIUM) — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CWECWE-340 (generation of predictable numbers or identifiers)
NVD statusAnalyzed
NVD publication2026-11-03
Added to CISA KEV2026-10-30
CISA due date2026-11-13
Ransomwareunknown per CISA

NVD description:

Use of predictable filenames in Ivanti Connect Secure before versions 25.1.1.3 and 22.8R2.6 allows a remote authenticated attacker to upload files with attacker-controlled content to a known location on disk.


What the flaw does

Connect Secure uses predictable filenames when handling an upload. An authenticated attacker can therefore upload a file with content of their choosing and know exactly where it lands on disk.

On its own, that is not much: no data disclosure (C:N), no availability impact (A:N), low integrity impact (I:L), and an account is required. Hence the 4.3.

Why it is in KEV

CISA states it can be chained with CVE-2026-104935 and CVE-2026-111357. Put in order:

  1. CVE-2026-104935: authentication bypass and command execution without an account (our October 14 article). The "authenticated" requirement of CVE-2026-118527 goes away.
  2. CVE-2026-118527: an attacker-controlled file is dropped at a known location.
  3. CVE-2026-111357: escalation to root, which NVD ties to the way the dsinvoked broker trusts DSCache configuration data.

Neither CISA nor NVD spells out how steps 2 and 3 connect. A likely reading, and it is only an inference: a file sitting at a known path is exactly what an escalation needs when it relies on data a privileged component reads. That is the classic role of a chain link: harmless alone, essential in combination.

It is also a perfect example of where score-based triage breaks down. A 4.3 that requires an account never surfaces on a dashboard, yet it helps take full control of a VPN gateway.


Affected versions per NVD

BranchNVD boundsFirst version out of range
25.1from 25.1.0.0, up to but excluding 25.1.1.325.1.1.3
22.8R222.8R2, R2.1, R2.2, R2.3, R2.4 and R2.5 listed individually22.8R2.6 (per the description)

These are the same bounds as for CVE-2026-111357. They are bounds, not necessarily the release Ivanti recommends. To know what to install, the reference remains Ivanti's security advisory on CVE-2026-104935, cited by both NVD and CISA, which covers the whole chain.


Detection

  • Ivanti's Integrity Checker Tool (ICT): before and after upgrading
  • Unexpected files on the appliance, especially in upload locations: that is precisely what this CVE enables
  • Authenticated sessions with no matching user login in the logs, which would point to CVE-2026-104935
  • Root-owned processes or files that do not match the expected image
  • Outbound connections from the appliance to unknown destinations

If your appliance was exposed on a version vulnerable to CVE-2026-104935, assume the whole chain may have been run.


Mitigation

  1. Apply the fixed release Ivanti specifies, at minimum beyond the NVD bounds (25.1.1.3 or 22.8R2.6). The CISA due date for this CVE is November 13; the deadlines for the other two links have already passed.
  2. Run the ICT and keep the results.
  3. If anything looks off: follow Ivanti's response procedure (factory reset or rebuild), then rotate every secret the appliance held.
  4. Restrict the admin interface to a management network and limit what the appliance can reach internally.

Why continuous monitoring of your VPN gateways matters

Three CVEs, three KEV dates, scores ranging from 4.3 to none at all, and an NVD entry that showed up four days after the catalog listing. Tracking a chain like this by hand is how you miss a link.

With cveo.tech, register your Connect Secure appliances with their exact version and get an alert as soon as a CVE affecting them is added to the CISA KEV catalog, whatever its score.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.