DE EN IT

~/exploited / cve-2026-118527

CVE-2026-118527: Ivanti Connect Secure

According to CISA this vulnerability is already used in attacks (added on 30 October 2026).

Key facts

CVECVE-2026-118527
VendorIvanti — Connect Secure
VulnerabilityIvanti Connect Secure Generation of Predictable Numbers or Identifiers Vulnerability
Added30 October 2026
Deadline (US agencies)13 November 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score4.3 (medium) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Attack over the network, complexity: low, privileges: low needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 0.82%. Higher than 58.1% of all scored vulnerabilities (as of 19 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks.
Weakness type (CWE)CWE-340
Affected versionsconnect secure: >= 25.1.0.0, < 25.1.1.3
connect secure 22.8

Description (NVD)

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.

Patches and vendor advisories

Description (CISA)

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.

Required action (CISA)

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What admins should do now

  1. Affected? Check whether Ivanti Connect Secure is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 30 October 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).