CVE-2025-22457
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.
do firstApply mitigations as set forth in the CISA instructions linked below.
Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.
Cloudflare · 1 rule (Disabled) · since 22 Apr 2025
- Ivanti - Buffer Error - CVE:CVE-2025-22457 · Cloudflare Managed Ruleset
Also consider: patch · enable the vendor rule in block mode
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-22457 being exploited?
Yes. CVE-2025-22457 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-22457?
CVE-2025-22457 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-22457?
Yes. A fix has been recorded for CVE-2025-22457. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-22457 affect?
CVE-2025-22457 affects ivanti:connect_secure, ivanti:policy_secure, ivanti:zero_trust_access_gateway. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
public exploits
Public exploit code: 1 Metasploit module · 6 GitHub proofs of concept
- sfewer-r7/CVE-2025-22457 · 73 ★
- securekomodo/CVE-2025-22457 · 18 ★
- Vinylrider/ivantiunlocker · 2 ★
- TRone-ux/CVE-2025-22457 · 1 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 3 Apr 2025 (SSVC 2.0.3).
timeline
- 3 Apr 2025CISA SSVC assessment: exploitation active
- 3 Apr 2025Published · 1 day later
- 4 Apr 2025Added to CISA KEV (exploited in the wild) · same day later
- 8 Apr 2025First public exploit or proof of concept · 4 days later
- 11 Apr 2025CISA remediation due date (US federal agencies) · 3 days later
- 4 Aug 2026CVE record last updated · 480 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 91 days (about 3 months) later
- Linkforums.ivanti.com /s/article/April-Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gatew
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-22457
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Metasploit Framework: exploit and scanner modules
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.