dbcve.org
Connect SecureApplication · Ivanti

CVE-2025-5462

HIGH · 7.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 22.7 / 22.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A heap-based buffer overflow in Ivanti Connect Secure before 22.7R2.8 or 22.8R2, Ivanti Policy Secure before 22.7R1.5, Ivanti ZTA Gateway before 22.8R2.3-723 and Ivanti Neurons for Secure Access before 22.8R1.4 (Fix deployed on 02-Aug-2025) allows a remote unauthenticated attacker to trigger a denial of service.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A heap-based buffer overflow vulnerability exists in multiple Ivanti products (Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access) in versions prior to the specified patches. The flaw allows a remote unauthenticated attacker to trigger a denial of service condition through the buffer overflow.

MitigationApply the vendor-supplied patches (22.7R2.8/22.8R2 for Connect Secure, 22.7R1.5 for Policy Secure, 22.8R2.3-723 for ZTA Gateway, and 22.8R1.4 for Neurons) deployed as of August 2, 2025, or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Connect SecureApplication
Affected:< 22.7= 22.7
Policy SecureApplication
Affected:< 22.7= 22.7
Zero Trust Access GatewayApplication
Affected:= 22.8
Neurons For Secure AccessApplication
Affected:< 22.8= 22.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Ivanti product
    Access the admin console or check system documentation to determine which Ivanti product is deployed: Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access.
    Affected if Any of these four products is installed.
  2. Check Ivanti Connect Secure version
    Navigate to the admin console, go to System > Configuration > System Management, or use the CLI command 'show version' to retrieve the installed version.
    Affected if Version is less than 22.7 OR equals 22.7 exactly.
  3. Check Ivanti Policy Secure version
    Navigate to the admin console, go to System > Configuration > System Management, or use the CLI command 'show version' to retrieve the installed version.
    Affected if Version is less than 22.7 OR equals 22.7 exactly.
  4. Check Ivanti Zero Trust Access Gateway version
    Navigate to the admin console or use the CLI command 'show version' to retrieve the installed version.
    Affected if Version equals exactly 22.8.
  5. Check Ivanti Neurons for Secure Access version
    Navigate to the admin console or use the CLI command 'show version' to retrieve the installed version.
    Affected if Version is less than 22.8 OR equals 22.8 exactly.

A user is affected if they have any of the four listed Ivanti products installed AND the installed version matches the specific affected version ranges for that product.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.7 / 22.8 or later
Fixed in 22.722.8
Interim mitigation

Apply the vendor-supplied patches (22.7R2.8/22.8R2 for Connect Secure, 22.7R1.5 for Policy Secure, 22.8R2.3-723 for ZTA Gateway, and 22.8R1.4 for Neurons) deployed as of August 2, 2025, or later.

Recommended fix High confidence

Connect Secure: 22.7R2.8 or 22.8R2; Policy Secure: 22.7R1.5; ZTA Gateway: 22.8R2.3-723; Neurons for Secure Access: 22.8R1.4

  1. 1. Identify the exact Ivanti product version currently deployed (Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access).
  2. 2. Download the appropriate fixed version from Ivanti's official support portal: For Connect Secure, upgrade to 22.7R2.8 or 22.8R2; For Policy Secure, upgrade to 22.7R1.5; For ZTA Gateway, upgrade to 22.8R2.3-723; For Neurons for Secure Access, upgrade to 22.8R1.4.
  3. 3. Review Ivanti upgrade documentation and release notes for the target version before initiating the upgrade.
  4. 4. Create a full backup of the current configuration.
  5. 5. Schedule a maintenance window as the upgrade may require downtime.
  6. 6. Perform the upgrade following Ivanti's standard upgrade procedure for the specific product.
  7. 7. After upgrade, verify the system is operational and confirm the new version is running.
  8. 8. Test critical functionalities to ensure normal operation post-upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connect Secure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5462 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5462 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data