# Ivanti Connect Secure needs the second October patch

Canonical: https://www.oktsec.com/radar/ivanti-connect-secure-october-2026-exploited-flaws
Publisher: Oktsec
Language: en
Published: 2026-11-21T21:23:51Z
Updated: 2026-11-21T21:23:51Z
Record reviewed: 2026-11-21T21:23:51Z
Latest evidence check: 2026-11-21T21:23:51Z
Disclosed: 2026-10-29

CISA lists both an authenticated file upload and a local privilege escalation in Connect Secure as exploited. Appliances on the initial October fixes still require the subsequent security update.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Act now
- Rationale: Both CVEs entered CISA KEV on October 30. In the observed chain, exploitation could lead to root access on an edge appliance.
- Evidence: Attacks confirmed
- Verification: Multiple sources
- Fix status: Fix available
- Exposure requirement: Application or configuration dependent
- Vendor: Ivanti
- Products: Ivanti Connect Secure
- CVEs: CVE-2026-111357, CVE-2026-118527

## Technical overview

CVE-2026-118527 permits an authenticated user to upload files to a predictable location. Ivanti’s CNA record names 22.8R2.6 and 25.1.1.3 as corrected. CVE-2026-111357 is a local privilege escalation. Its CNA record identifies an affected 22.8R2.4 appliance but does not enumerate all branches. Rapid7’s per-CVE remediation table identifies the same two fixes for both issues.

The October 13 releases addressed an earlier authentication flaw. Verify the actual build on the appliance even if that original update was installed.

## Recommended response

Check each appliance and cluster member. On 22.8R2, verify 22.8R2.6 or a later supported fix. On 25.1.1, verify 25.1.1.3 or a later supported fix. Investigate exposure before the update and rotate credentials if compromise is suspected.

Relevant to: Network and incident response teams operating Ivanti Connect Secure.

## CVE attribution

- CVE-2026-111357: Ivanti — Ivanti Connect Secure. [Source](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/111xxx/CVE-2026-111357.json)
- CVE-2026-118527: Ivanti — Ivanti Connect Secure. [Source](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/118xxx/CVE-2026-118527.json)

## Affected systems and fixes

### Connect Secure 22.8R2

Affected: 22.8R2.5 and earlier in this branch.

Fixed release / action: 22.8R2.6

### Connect Secure 25.1.1

Affected: 25.1.1.2 and earlier in this branch.

Fixed release / action: 25.1.1.3

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.20
Checked: 2026-11-21T21:27:34.352Z

### [CVE-2026-111357](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-111357)

- Added: 2026-10-30
- Ransomware use: Not confirmed by CISA
- Federal due date: 2026-11-02
- Federal forensic triage: Yes

Action specified by 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.

### [CVE-2026-118527](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-118527)

- Added: 2026-10-30
- Ransomware use: Not confirmed by CISA
- Federal due date: 2026-11-13
- Federal forensic triage: No

Action specified by 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.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-22T13:41:03.396Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-118527](https://api.first.org/data/v1/epss?cve=CVE-2026-118527): 0.99% probability of observed exploitation in the next 30 days; percentile 63.39%; score date 2026-11-21.
- [CVE-2026-111357](https://api.first.org/data/v1/epss?cve=CVE-2026-111357): 0.8% probability of observed exploitation in the next 30 days; percentile 57.62%; score date 2026-11-21.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-22T13:41:03.396Z.

## Response checklist

1. **Identify exposed appliances** — Record the appliance model, branch and running build of every cluster member.
2. **Verify the second October fix** — Confirm the corrected build on each node. Use the vendor’s model-specific guidance for other branches.
3. **Investigate prior exposure** — Preserve logs and available forensic records. Review unusual access and investigate possible credential theft separately from the upgrade.

## Relevance to AI environments

Check service identities or automation credentials that a compromised appliance could access.

## Sources

- [Connect Secure privilege escalation on 22.8R2.4](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/111xxx/CVE-2026-111357.json) — MITRE; Research report; checked 2026-11-21T21:23:51Z
- [Ivanti CNA record for the authenticated file upload](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/118xxx/CVE-2026-118527.json) — Ivanti; Vendor notice; checked 2026-11-21T21:23:51Z
- [Known Exploited Vulnerabilities catalog](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json) — CISA; Government advisory; checked 2026-11-21T21:23:51Z
- [AV26-1035, October 30 update](https://www.cyber.gc.ca/en/alerts-advisories/ivanti-security-advisory-av26-1035) — Canadian Centre for Cyber Security; Government advisory; checked 2026-11-21T21:23:51Z
- [October 29 remediation table for each vulnerability](https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527/) — Rapid7; Research report; checked 2026-11-21T21:23:51Z

## Editorial record

- 2026-11-21T21:23:51Z: Matched both October 30 KEV entries and documented the second update for the 22.8R2 and 25.1.1 branches.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/ivanti-connect-secure-october-2026-exploited-flaws) · [Build a response plan](https://www.oktsec.com/radar/ivanti-connect-secure-october-2026-exploited-flaws#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=ivanti-connect-secure-october-2026-exploited-flaws&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=ivanti-connect-secure-october-2026-exploited-flaws&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

