CriticalCVE-2025-0282

    Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow Vulnerability (CVE-2025-0282)

    Published Last modified In CISA KEV since Sources: pwn.watch, CVE.org, SingCERT, NCSC NZ

    What is affected, what to do

    A stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.5, Ivanti Policy Secure before version 22.7R1.2, and Ivanti Neurons for ZTA gateways before version 22.7R2.3 allows a remote unauthenticated attacker to achieve remote code execution.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Ivanti Connect Secure lte 22.7R2..22.7R2.4
    • Ivanti Policy Secure lte 22.7R1..22.7R1.2
    • Ivanti Neurons for ZTA gateways lte 22.7R2..22.7R2.3

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.0

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: pwn.watch, CVE.org, SingCERT, NCSC NZ

    99.98 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.98

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    257.46 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab), ANSSI / CERT-FR, NCSC NZ, CSA/SingCERT How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    99.98 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.98
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-121

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This is unauthenticated remote code execution on a perimeter device that is internet-facing by design and brokers credentials into the internal network. The high attack-complexity rating in the CVSS vector offers little real protection: public exploits exist and exploitation likelihood is among the highest of any CVE. CISA flags known use in ransomware campaigns. Typical victims are organisations that rely on Ivanti VPN as their primary remote-access path, including government, critical infrastructure, manufacturing and managed service providers. Treat any unpatched, internet-exposed instance as a top-priority emergency and assume compromise until integrity checks and log review prove otherwise. Under NIS2, assess incident-reporting deadlines early.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Run integrity checks before patching: On every Ivanti Connect Secure, Policy Secure and ZTA gateway, run both the internal and external Integrity Checker Tool (ICT) and preserve the output. Upgrading first can overwrite evidence of compromise. A clean ICT result does not guarantee the appliance is clean, so apply the detection rules below as well.
      • If ICT flags anything or compromise is suspected: Isolate the appliance and capture a forensic image plus all logs, including the syslog/SIEM copies. Then perform a factory reset and rebuild directly on the fixed version. Do not upgrade a compromised box in place.
      • Patch: Upgrade Ivanti Connect Secure to 22.7R2.5 or later and Ivanti Neurons for ZTA gateways to 22.7R2.3 or later. Upgrade Ivanti Policy Secure to 22.7R1.2 or later, and confirm build availability in the vendor advisory. Check legacy 9.x branches for support status and a migration path.
      • Rotate secrets: On suspected compromise, treat every secret on or behind the appliance as exposed. This covers local admin accounts, LDAP/AD bind and service accounts, RADIUS shared secrets, API keys, and TLS certificates and private keys. Terminate active VPN sessions and reset passwords for privileged VPN users.
      • Inventory exposure: Use ASM scans or Shodan/Censys lookups to find every internet-facing Ivanti gateway on TCP 443, including forgotten lab and test appliances. Policy Secure should never be internet-reachable.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Restrict the admin interface (admin URL or dedicated management port) to a management VLAN or jump-host zone. Apply default-deny egress from the appliance, allowing only required destinations: AD/LDAP, RADIUS, DNS, NTP, syslog and Ivanti update servers. This disrupts reverse shells and tool staging.
      • Contain lateral movement: Treat the gateway's internal interface as an untrusted zone. Allow only the destinations and ports the appliance genuinely needs. Permit SMB, RDP, WinRM and SSH to servers and domain controllers only where explicitly required.
      • IPS/WAF: Enable upstream IPS signatures for CVE-2025-0282 (Suricata ET and the major NGFW vendors ship them). Alert on or block malformed or oversized IF-T/TLS handshakes, i.e. HTTP Upgrade: IF-T/TLS 1.0 with abnormally long client-capability fields.
      • Access restriction: Where the business allows it, temporarily limit VPN access with geo-IP or allowlist filtering to expected countries and partner ranges. On ZTA, restrict who can reach the controller.
      • Logging resilience: Forward all event, admin and access logs to an external SIEM via syslog. On-box logs can be wiped or tampered with after compromise.

    3. Runbook step 3

      Detection rules

      • Network telemetry (Zeek/Suricata): Flag HTTP requests to the gateway carrying Upgrade: IF-T/TLS from unfamiliar sources, especially when followed by resets or repeated attempts. Sigma shape: http.request.headers.upgrade|contains: 'IF-T/TLS', aggregated by source with a rate threshold.
      • Appliance egress: Treat any outbound connection from the appliance IP to a non-allowlisted destination as suspicious, particularly VPS/hosting ASNs, unusual ports, or DNS lookups for newly registered domains. KQL example: CommonSecurityLog | where SourceIP == "<appliance-ip>" and DestinationIP !in (allowlist).
      • Appliance logs in SIEM: Watch for web process crashes or restarts, gaps in log continuity, cleared or abruptly truncated logs, unexpected admin logins, and config or system-update events outside change windows. Also watch for ICT runs that fail or restart unexpectedly.
      • AD lateral movement (Windows events): Look for VPN service accounts authenticating from the appliance IP to unusual hosts (4624 logon type 3/10, 4768/4769), bulk LDAP enumeration, and new accounts or group memberships (4720, 4728, 4732). Prioritise events that line up in time with gateway anomalies.
      • EDR on internal hosts: Hunt for RDP, SMB or SSH sessions sourced from the VPN address pool that lead to tunnelling tools, credential dumping (LSASS access, Sysmon EID 10), or ransomware precursors such as backup deletion and vssadmin delete shadows.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    A stack-based buffer overflow in Ivanti Connect Secure before version 22.7R2.5, Ivanti Policy Secure before version 22.7R1.2, and Ivanti Neurons for ZTA gateways before version 22.7R2.3 allows a remote unauthenticated attacker to achieve remote code execution.

    Source: pwn.watch, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE), cvelistv5, CSA/SingCERT, NCSC NZ (CC BY 4.0)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    IvantiConnect Secure
    • 22.7R2 – ≤ 22.7R2.4
    • —
    IvantiNeurons for ZTA gateways
    • 22.7R2 – ≤ 22.7R2.3
    • —
    IvantiPolicy Secure
    • 22.7R1 – ≤ 22.7R1.2
    • —
    ivanticonnect_secure
    • 22.7
    • —
    ivantineurons_for_zero-trust_access
    • 22.7
    • —
    ivantipolicy_secure
    • 22.7
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-121Stack-based Buffer Overflow

      Variant

      A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

      Entry at MITRE CWE-121

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    CSA/SingCERTActive Exploitation of Critical Zero-Day Vulnerability in Ivanti Connect Secure (opens in a new tab)CSA/SingCERTactively exploited
    NCSC NZTwo vulnerabilities affecting Ivanti products (opens in a new tab)NCSC NZactively exploited
    ANSSI / CERT-FRLicence Ouverte 2.0, as of CERTFR-2025-ALE-001 – [MàJ] Vulnérabilité dans les produits Ivanti (clôturée 2025-05-07) (opens in a new tab)cert.cyber.gouv.fractively exploited
    GitHubsfewer-r7/CVE-2025-0282 (opens in a new tab)github.comPoC (publicly reported)reported, not verified—
    PoC-in-GitHub (nomi-sec)cve-2025-0282-ivanti_rce_reproduction (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • forums.ivanti.coms/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure…
    • labs.watchtowr.comexploitation-walkthrough-and-techniques-ivanti-connect-secure-r…Third-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?search_api_fulltext=CVE…government-resource
    • github.comsfewer-r7/CVE-2025-0282Exploit
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0282government-resource
    • cisa.govCISA Mitigation Instructions for CVE-2025-0282pwn-watch
    • cloud.google.comblog/topics/threat-intelligence/ivanti-connect-secure-vpn-zero-…
    • cert.cyber.gouv.frANSSI / CERT-FR: CERTFR-2025-ALE-001 – [MàJ] Vulnérabilité dans les produits Ivanti (clôturée 2025-05-07)cert-fr
    • pwn.watchpwn.watch: Ivanti Connect Secure zero-day exploited since mid-December 2024 (CVE-2025-0282)pwn-watch
    • cloud.google.comIvanti Connect Secure VPN Targeted in New Zero-Day Exploitationpwn-watch
    • rapid7.comCVE-2025-0282: Ivanti Connect Secure Zero-Day Exploited in the Wildpwn-watch
    • NCSC UKActive exploitation of vulnerability affecting Ivanti Connect Securepwn-watch
    • NVD (NIST)NVD: CVE-2025-0282pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modified3c1d8aa1…

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-0282-CVE-2025-0283
      Referenceremoved
      https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-0282-CVE-2025-0283
      —
      Reference typeremoved
      https://forums.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-Policy-Secure-ZTA-Gateways-CVE-2025-0282-CVE-2025-0283 Types: Vendor Advisory
      —

      Source identifier: 3c1d8aa1-5a33-4ea4-8992-aadd6440af75

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: no

      Show 14 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://github.com/sfewer-r7/CVE-2025-0282
      Referenceadded
      —
      https://labs.watchtowr.com/exploitation-walkthrough-and-techniques-ivanti-connect-secure-rce-cve-2025-0282/
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0282
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2025-0282
      Referenceremoved
      https://github.com/sfewer-r7/CVE-2025-0282
      —
      Referenceremoved
      https://labs.watchtowr.com/exploitation-walkthrough-and-techniques-ivanti-connect-secure-rce-cve-2025-0282/
      —
      Referenceremoved
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0282
      —
      Referenceremoved
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2025-0282
      —
      Reference typeremoved
      https://github.com/sfewer-r7/CVE-2025-0282 Types: Exploit
      —
      Reference typeremoved
      https://labs.watchtowr.com/exploitation-walkthrough-and-techniques-ivanti-connect-secure-rce-cve-2025-0282/ Types: Exploit, Third Party Advisory
      —
      Reference typeremoved
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-0282 Types: US Government Resource
      —
      Reference typeremoved
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2025-0282 Types: US Government Resource
      —
      SSVC assessmentremoved
      {"id":"CVE-2025-0282","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2025-01-08T00:00:00+00:00"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2025-0282","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-04T03:55:37.816415Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Record modifiedCVE Program

      Show 6 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://cloud.google.com/blog/topics/threat-intelligence/ivanti-connect-secure-vpn-zero-day
      Referenceadded
      —
      https://www.cisa.gov/cisa-mitigation-instructions-cve-2025-0282
      Referenceremoved
      https://cloud.google.com/blog/topics/threat-intelligence/ivanti-connect-secure-vpn-zero-day
      —
      Referenceremoved
      https://www.cisa.gov/cisa-mitigation-instructions-cve-2025-0282
      —
      Reference typeremoved
      https://cloud.google.com/blog/topics/threat-intelligence/ivanti-connect-secure-vpn-zero-day Types: Exploit, Technical Description
      —
      Reference typeremoved
      https://www.cisa.gov/cisa-mitigation-instructions-cve-2025-0282 Types: Third Party Advisory, US Government Resource
      —

      Source identifier: af854a3a-2127-422b-91ae-364da2661108

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-0282
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-0282"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-0282.svg?lang=en" alt="CVE-2025-0282 – NEOSEC Intel" height="20"></a>