Quick answer
Yes. CVE-2026-111357 in Ivanti Connect Secure is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on October 30, 2026. If you run Connect Secure, apply the vendor's fix now and check for signs of compromise.
What is CVE-2026-111357?
Ivanti Connect Secure Missing Authentication for Critical Function Vulnerability. Ivanti Connect Secure contains a missing authentication for critical function vulnerability that could allow a local authenticated attacker to escalate their privileges. This vulnerability can be chained with CVE-2026-104935 and CVE-2026-118527.
Description from the CISA Known Exploited Vulnerabilities catalogue.
What kind of flaw is it?
A sensitive function can be used without logging in at all.
Other exploited missing authentication for a critical functionThe system checks who you are but not whether you are allowed to do the thing you asked.
Other exploited missing authorization How it worksWhy it matters
Internet-facing VPNs, firewalls and gateways are the most targeted systems in current intrusions. They sit on the perimeter, often run with high privilege and rarely have endpoint protection, so one exploited flaw can hand an attacker a foothold inside the network.
Higher than 46% of all scored vulnerabilities.
Am I affected? How to check | What to do now |
|---|---|
1Confirm whether you run the affected product, including devices managed by your IT provider. | 1Apply the vendor's fixed version or mitigation immediately. |
2Check the installed firmware or software version against the vendor advisory. | 2Remove internet access to management interfaces. |
3Check whether the management interface or VPN portal is reachable from the internet. | 3If the device was exposed and unpatched, treat it as potentially compromised: hunt for indicators, rotate credentials and VPN secrets, and consider a forensic review. |
4Review device logs for unexpected logins, new admin accounts or configuration changes since the vulnerability was disclosed. | 4Send device logs to a central log store so evidence survives if the device is compromised again. |
Am I affected? How to check
- 1Confirm whether you run the affected product, including devices managed by your IT provider.
- 2Check the installed firmware or software version against the vendor advisory.
- 3Check whether the management interface or VPN portal is reachable from the internet.
- 4Review device logs for unexpected logins, new admin accounts or configuration changes since the vulnerability was disclosed.
What to do now
- 1Apply the vendor's fixed version or mitigation immediately.
- 2Remove internet access to management interfaces.
- 3If the device was exposed and unpatched, treat it as potentially compromised: hunt for indicators, rotate credentials and VPN secrets, and consider a forensic review.
- 4Send device logs to a central log store so evidence survives if the device is compromised again.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
Deadline and priority
CISA requires US federal civilian agencies to remediate catalogued vulnerabilities by the listed due date under Binding Operational Directive 22-01 (November 2, 2026 for this one), and strongly urges every organization to prioritize them the same way.
Common questions
Is CVE-2026-111357 being exploited?
Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on October 30, 2026.
How do I fix CVE-2026-111357?
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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. Check the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.
Is my Ivanti Connect Secure affected?
Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.