Exploited CVEs / Ivanti / CVE-2025-22457

CVE-2025-22457

Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted, and the vulnerability is known to be used in ransomware campaigns. Federal agencies were required to remediate by 2025-04-11 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Ivanti Security Advisories, linked below.

Risk summary

CriticalCISA KEVRansomware
9.8
CVSS v3 base
100%
EPSS exploit probability
Critical
Severity
2025-04-04
Added to KEV
2025-04-11 (past due)
CISA due date

Actively exploited Ivanti Connect Secure, Policy Secure, and ZTA Gateways vulnerability, Critical severity, CVSS v3 9.8. Added to the CISA KEV catalog 2025-04-04.

Senserva AI read on CVE-2025-22457CISA required actionOfficial fix for CVE-2025-22457Admin questions#85 hottest CVE right now

Senserva AI Opinion for CVE-2025-22457

A stack-based buffer overflow in Ivanti Connect Secure, Policy Secure, and ZTA Gateways giving remote unauthenticated code execution, CVSS 9.8, EPSS 100%, with ransomware use confirmed. VPN gateways remain the most consequential perimeter target there is, and this April 2025 KEV entry continued Ivanti's run of actively exploited edge flaws.

Do this: Patch affected Ivanti gateways and run integrity checks for implants on any device that sat exposed while vulnerable.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2025-22457

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch immediately
Exploited in the wild and used in ransomware campaigns.
The fix ships from the vendor: Ivanti Security Advisories.
Do this now: Move this ahead of everything else in the queue, then verify the fix actually landed on every exposed device.

Updated September 3, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2025-22457

Published
2025-04-04
Last revised
2025-04-04
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when
0%25%50%75%100%CISA KEVCISA KEV on 2025-04-042026-07-17: EPSS 100%2026-07-24: EPSS 100%2026-08-04: EPSS 100%2026-08-10: EPSS 100%2026-08-30: EPSS 100%2026-08-30: EPSS 100%EPSS 100%2025-04-042026-08-30

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2025-04-04 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 9.8; EPSS first scored at 100.0%
  • 2026-07-24 EPSS 100.0% to 99.9%
  • 2026-08-04 EPSS 99.9% to 100.0%
  • 2026-08-30 EPSS 100.0% to 100.0%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2025-04-11 (past due).

Apply mitigations as set forth in the CISA instructions linked below.

Official fix for CVE-2025-22457

The authoritative fix and affected-version list are published by the vendor. Find the Connect Secure, Policy Secure, and ZTA Gateways advisory on Ivanti Security Advisories.

Common questions about CVE-2025-22457

Is CVE-2025-22457 actively exploited?

Yes. CVE-2025-22457 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2025-04-04, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 100%. CISA also reports it is known to be used in ransomware campaigns.

What is the CISA deadline and required action for CVE-2025-22457?

CISA set the federal (BOD 22-01) remediation due date at 2025-04-11, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations as set forth in the CISA instructions linked below.

What fixes CVE-2025-22457?

The authoritative fix is in the vendor advisory: see Ivanti Security Advisories for the patched Connect Secure, Policy Secure, and ZTA Gateways versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2025-22457?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2025-22457's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed once a day (early morning US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.