# CVE-2025-22457: Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow

> Remote unauthenticated attackers can achieve code execution via a stack-based buffer overflow in Ivanti Connect Secure, Policy Secure, and ZTA Gateways.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 4 Apr 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-jjr5-fpcg-gc53

## What is CVE-2025-22457?

CVE-2025-22457 is a critical memory corruption vulnerability in Ivanti Connect Secure, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-22457?

It affects 3 products.


Products: Ivanti Connect Secure, Ivanti Policy Secure, Ivanti Zero Trust Access Gateway.

## How do I fix CVE-2025-22457?

No fix has been published for CVE-2025-22457 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 11 Apr 2025.

## Is CVE-2025-22457 being exploited?

Yes. Attackers have exploited CVE-2025-22457 in the wild since at least 4 Apr 2025, including in ransomware campaigns.

Public exploit code:

- PoC for CVE-2025-22457 - A remote unauthenticated stack based buffer overflow affecting Ivanti Connect Secure, Pulse Connect Secure, Ivanti Policy Secure, and ZTA Gateways (github_poc): https://github.com/sfewer-r7/CVE-2025-22457
- CVE-2025-22457: Python Exploit POC Scanner to Detect Ivanti Connect Secure RCE (github_poc): https://github.com/securekomodo/CVE-2025-22457
- Prevent CVE-2025-22457 and other security problems with Juniper/Ivanti Secure Connect SSL VPN (github_poc): https://github.com/Vinylrider/ivantiunlocker
- PoC CVE-2025-22457 (github_poc): https://github.com/TRone-ux/CVE-2025-22457
- Ivanti Connect Secure Unauthenticated Remote Code Execution via Stack-based Buffer Overflow (metasploit)
- Altay takımı haftalık sunumu için yaptığım cve-2025-22457 zafiyeti demo uygulaması (github_poc): https://github.com/benmevic/cve-2025-22457

## Other vulnerabilities in Ivanti Connect Secure

- [CVE-2021-22893](https://insights.sbomify.com/CVE-2021-22893/): Ivanti Pulse Connect Secure Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2019-11510](https://insights.sbomify.com/CVE-2019-11510/): Ivanti Pulse Connect Secure Arbitrary File Read (critical 9.9, exploited in the wild)
- [CVE-2024-21887](https://insights.sbomify.com/CVE-2024-21887/): Ivanti Connect Secure and Policy Secure Command Injection (critical 9.1, exploited in the wild)
- [CVE-2025-0282](https://insights.sbomify.com/CVE-2025-0282/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)
- [CVE-2021-22894](https://insights.sbomify.com/CVE-2021-22894/): Ivanti Pulse Connect Secure Collaboration Suite Buffer Overflow (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22457 and fix it if it is affected.

What it is: CVE-2025-22457 is a critical memory corruption vulnerability in Ivanti Connect Secure, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-22457 in the wild since at least 4 Apr 2025, including in ransomware campaigns.

Affected product: Ivanti Connect Secure. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22457/ (Markdown: https://insights.sbomify.com/CVE-2025-22457/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22457
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22457
- OSV: https://osv.dev/vulnerability/CVE-2025-22457

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22457/
Summaries are generated and may contain mistakes; the official description above is the record.