Threats / Ivanti / CVE-2025-22457
CVE-2025-22457
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Ivanti Connect Secure, Policy and ZTA Gateways vulnerability
Stack-based buffer overflow in Ivanti Connect Secure, Policy Secure, and ZTA Gateways allows unauthenticated remote code execution.
Verdict
Today item, not a backlog item.
A stack-based buffer overflow vulnerability in Ivanti gateway products enables remote attackers to execute arbitrary code without authentication. Active exploitation and ransomware deployment have been observed.
CISA KEV Yes · 2025-04-045Ransomware use Flagged5EPSS 0.99932 (verify live)6Exploit Weaponized · public PoC7CVSS 93CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
26 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-04-04), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99932 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) · Affected: Ivanti, Connect Secure, Policy Secure, and ZTA Gateways. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-121 Stack-based Buffer Overflow — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious network request that overflows a stack buffer in the vulnerable gateway service.
Business
The organization's perimeter security is bypassed, exposing internal networks to direct compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I achieve code execution on the gateway with the privileges of the vulnerable service process.
Business
Attackers gain a foothold to pivot toward critical infrastructure, databases, and sensitive systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence and deploy ransomware payloads across the compromised environment.
Business
Operations halt, data is encrypted, and the organization faces extortion demands and potential data breach disclosure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05