Threats / Ivanti / CVE-2025-0282
CVE-2025-0282
· 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 enables unauthenticated remote code execution. Actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
Critical unauthenticated RCE via memory corruption. High exploitation likelihood (EPSS 0.94) with confirmed active abuse in ransomware operations. Immediate patching required for all affected gateway deployments.
CISA KEV Yes · 2025-01-085Ransomware use Flagged5EPSS 0.99971 (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
60 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-01-08), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99971 — 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 the same day 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 public proof-of-concept / detection template). Catalog entries: nuclei template. 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 the stack buffer in the gateway's input handler, bypassing authentication checks.
Business
Attackers gain direct code execution on security perimeter devices without credentials, establishing initial compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary commands with gateway privileges to establish persistence and lateral movement into the internal network.
Business
Ransomware operators pivot from gateway to internal systems, encrypting critical data and demanding payment.
3
Lateral reach — past segmentation narrative 3
Attacker
I exfiltrate sensitive data passing through the gateway or stored on the compromised device before deploying encryption payloads.
Business
Double-extortion tactics increase pressure on victims; data breach notifications trigger regulatory and reputational damage.
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