IRONSMITHINTEL
CRITICALCVSS9.0
|
Actively Exploited
|CISA KEV|CVE-2025-0282|Auth: none — unauthenticated|Reboot: required|Manual only

Ivanti Connect Secure, Policy Secure, and ZTA Gateways < 22.7 — RCE

Ivanti Connect Secure, Policy Secure, and ZTA Gateways contain a stack-based buffer overflow which can lead to unauthenticated remote code execution.

Published Jan 8, 2025 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. CISA has confirmed use of this vulnerability in known ransomware campaigns — treat as high priority for remediation. Federal agencies are required to remediate by 2025-01-15 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Stack-based Buffer Overflow (CWE-121) vulnerability in Ivanti Connect Secure, Policy Secure, and ZTA Gateways. A stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.5, Ivanti Policy Secure before version 22.7R1.2, and Ivanti Neurons for ZTA gateways before version 22.7R2.3 allows a remote unauthenticated attacker to achieve remote code execution. Exploitation requires remote network access, higher attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

Network Security Team
Firewall Administrators
IT Security
Running connect secure: 22.7; neurons for zero-trust access: 22.7; policy secure: 22.7
Fixed in22.7
Real-world incidentsWhat we've seen

Used in known ransomware campaigns. Threat-research write-up: https://cloud.google.com/blog/topics/threat-intelligence/ivanti-connect-secure-vpn-zero-day

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Upgrade to version 22.7 or later. Stage in a test ring before broad deployment.
3
Verify by checking the installed version on a sample of remediated hosts.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.