CVE Tools
Track your stack

CVE-2025-22457

Exploited in the wild. In CISA KEV since 2025‑04‑04. Fixed versions are out.

CVSS 3.19.0CriticalEPSS percentile99th100% chance in 30 daysCISA KEVListedsince 2025-04-04, due 2025-04-11
Public exploit: 1 sourceFix5 products3 fixed builds listed below

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Ivanti Neurons for ZTA gatewaysFixed builds22.8R2.2Stated by: CVE record
  • Ivanti Connect SecureAffected: < 22.7Upgrade to: 22.7Stated by: NVD
  • Ivanti Policy SecureAffected: < 22.7Upgrade to: 22.7Stated by: NVD
  • Ivanti Zero Trust Access GatewayAffected: < 22.8Upgrade to: 22.8Stated by: NVD
  • Ivanti Pulse Connect SecureAffected: до 22.7R2.6Upgrade to: not statedStated by: BDU

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Check it yourselfA free Nuclei and OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Discuss checks for your systems with a specialist. Scope is agreed before testing.

Coverage timeline

1 publisher

  1. Advisory coverage

    ·BleepingComputer summary

  2. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 1 further article named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
Public exploit
CISA KEV
CISA KEV

Listed as exploited in the wild since 2025-04-04.

US federal agencies must remediate by 2025-04-11.

Known use in ransomware campaigns.

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

1 source with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

100% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 133 days before any public exploit.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. EPSS band changehigh → critical
  4. Public exploit / PoCsource: github-poc
  5. Nuclei check added
  6. Patch availablerecord updated

Affected products

And 2 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Scored 9.0 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 1 more reference. See all after sign-in

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Connect Secure, not every advisory. This one: actively exploited.