CVE-2025-22457
Published: April 4, 2025
Official Description
Ivanti Connect Secure, Policy Secure, and ZTA Gateways contains a stack-based buffer overflow vulnerability that allows a remote unauthenticated attacker to achieve remote code execution.
CISA KEV Advisory
Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow Vulnerability
Ivanti Connect Secure, Policy Secure, and ZTA Gateways contains a stack-based buffer overflow vulnerability that allows a remote unauthenticated attacker to achieve remote code execution.
Apply mitigations as set forth in the CISA instructions linked below.
Risk Analysis
This vulnerability in Ivanti Connect Secure, Policy Secure, and ZTA Gateways allows a remote, unauthenticated attacker to achieve remote code execution due to a stack-based buffer overflow. Its inclusion in the KEV catalog and a high EPSS score indicate a significant and confirmed risk of exploitation.
This vulnerability is actively being exploited in the wild and is listed in CISA's KEV catalog, confirming its real-world exploitation.
Apply all available security patches and updates from Ivanti for Connect Secure, Policy Secure, and ZTA Gateways. Implement strong network perimeter defenses and monitor for suspicious activity.
Technical Analysis
CVE-2025-22457 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2025-22457 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2025-22457 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1