CVE-2025-22457: Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
A stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.6, Ivanti Policy Secure before version 22.7R1.4, and Ivanti ZTA Gateways before version 22.8R2.2 allows a remote unauthenticated attacker to achieve remote code execution.
Description quoted from the CVE record (assigned by ivanti, published 2025-04-03).
Weakness: CWE-121 Stack-based Buffer Overflow
How it can be exploited
Exploitable over the network with high attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.
- On CISA KEV since
- 2025-04-04
- US federal deadline
- 2025-04-11
- Ransomware use
- Yes
Public exploit evidence (Exploit Observer)
Also known as: BDU:2025-03788, CNNVD-202504-663, EUVD-2025-9646, GHSA-jjr5-fpcg-gc53
VEDAS cluster: VEDAS:BELLSHADOW
Exploit Observer links 10 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (10)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Metasploit module: https://www.rapid7.com/db/modules/exploit/linux/http/ivanti_connect_secure_stack_overflow_rce_cve_2025_22457/
- Nuclei template: https://raw.githubusercontent.com/projectdiscovery/nuclei-templates/main/code/cves/2025/CVE-2025-22457.yaml
- Code repository: https://github.com/b1ack4sh/blackash-cve-2025-22457
- Code repository: https://github.com/benmevic/cve-2025-22457
- Code repository: https://github.com/donofly/cve-2025-22457-vulnserver-lab
- Code repository: https://github.com/llussiess/cve-2025-22457
- Code repository: https://github.com/n4sl1/cve-2025-22457-poc
- Code repository: https://github.com/securekomodo/cve-2025-22457
- Code repository: https://github.com/sfewer-r7/cve-2025-22457
- Code repository: https://github.com/trone-ux/cve-2025-22457
Research and write-ups (3)
- Research or write-up: https://attackerkb.com/topics/0ybGQIkHzR/cve-2025-22457/rapid7-analysis
- Research or write-up: https://labs.watchtowr.com/is-the-sofistication-in-the-room-with-us-x-forwarded-for-and-ivanti-connect-secure-cve-2025-22457
- Research or write-up: https://www.rapid7.com/db/vulnerabilities/pulse-secure-pulse-connect-secure-cve-2025-22457
Vulnerability databases and vendor advisories (10)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://access.redhat.com/security/cve/cve-2025-22457
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2025-9646
- Vulnerability database or vendor advisory: https://forums.ivanti.com/s/article/April-Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-22457
- Vulnerability database or vendor advisory: https://forums.ivanti.com/s/article/April-Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-22457?language=en_US
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-jjr5-fpcg-gc53
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-22457
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-22457
- Vulnerability database or vendor advisory: https://www.cnnvd.org.cn/home/globalSearch?keyword=CNNVD-202504-663
- Vulnerability database or vendor advisory: https://www.cvedetails.com/cve/CVE-2025-22457
- Vulnerability database or vendor advisory: https://www.tenable.com/cve/CVE-2025-22457
349 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 1.000
very likely to be attacked soon - VEDAS
- 0.981
strong exploit evidence - On CISA KEV
- Yes, since 2025-04-04
- Detection rule
- None yet
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Ivanti Connect Secure | Not stated | 22.7R2.6 is not affected |
| Ivanti Policy Secure | Not stated | 22.7R1.4 is not affected |
| Ivanti Neurons for ZTA gateways | Not stated | 22.8R2.2 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: ivanti connect_secure, ivanti policy_secure, ivanti pulse_connect_secure_(eos), ivanti zero_trust_access_gateway, ivanti zta_gateways.
How to fix it
CISA required action: Apply mitigations as set forth in the CISA instructions linked below.
Vendor guidance:
- https://www.cisa.gov/cisa-mitigation-instructions-cve-2025-22457
- https://forums.ivanti.com/s/article/April-Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-22457
- https://nvd.nist.gov/vuln/detail/CVE-2025-22457
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
- Ivanti Connect Secure zero-day (CVE-2025-0282) (8 Jan 2025)
References
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-22457 (government-resource)
Other references
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.