The issue

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.

This description is sourced from CISA’s catalog. It is not a claim of original vulnerability discovery or testing.

Why it belongs on your radar

CISA added CVE-2026-118527 to its Known Exploited Vulnerabilities catalog on 2026-10-30. Use that exploitation signal alongside your own asset inventory and exposure when setting patch priorities.

The catalog records ransomware campaign use as “Unknown”. Unknown is not evidence that exploitation or ransomware use is absent.

What to do next

  1. Confirm whether you run Ivanti Connect Secure, including managed services and externally exposed instances. Assign an owner to the review.
  2. Use the vendor advisory to confirm affected versions, supported mitigations and fixed builds. Do not infer version coverage from the CVE identifier alone.
  3. Apply the relevant vendor update or mitigation through your change process. Check vendor guidance on investigation or compromise indicators as well as patching.
  4. Verify the deployed version and controls after the change, and record the affected assets and evidence of remediation.

CISA’s required action

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.

The catalog’s due date is 2026-11-13. Federal directive deadlines apply to covered organizations; other organizations should use their own risk and obligations to set the response timeline.

Sources & further reading

This brief summarizes public source material. Confirm affected versions and the current vendor instructions before changing production. No original exploit validation is claimed.