dbcve.org
Connect SecureApplication · Ivanti

CVE-2025-5468

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 22.7 / 22.8 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Improper handling of symbolic links in Ivanti Connect Secure before version 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 local authenticated attacker to read arbitrary files on disk.

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

Improper handling of symbolic links in multiple Ivanti products (Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access) allows a local authenticated attacker to read arbitrary files on the filesystem by creating or exploiting symbolic links that point to sensitive files.

MitigationApply the vendor-supplied patches: upgrade Ivanti Connect Secure to 22.7R2.8/22.8R2 or later, Policy Secure to 22.7R1.5 or later, ZTA Gateway to 22.8R2.3-723 or later, and Neurons for Secure Access to 22.8R1.4 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 the installed Ivanti product
    Access the admin console or run 'dmcli -e get system' to determine which Ivanti product is deployed (Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access)
    Affected if The system runs any of these four products and the version falls within affected ranges below
  2. Check Ivanti Connect Secure version
    Run 'dp get system.version' or access the admin dashboard under System > Configuration > System Management > System Information
    Affected if Version is < 22.7 or exactly 22.7 (versions 22.7R2.8/22.8R2 and later are fixed)
  3. Check Ivanti Policy Secure version
    Run 'dp get system.version' or access the admin dashboard under System > Configuration > System Management > System Information
    Affected if Version is < 22.7 or exactly 22.7 (version 22.7R1.5 and later are fixed)
  4. Check Ivanti Zero Trust Access Gateway version
    Run 'dp get system.version' or access the admin dashboard under System > Configuration > System Management > System Information
    Affected if Version is exactly 22.8 (version 22.8R2.3-723 and later are fixed)
  5. Check Ivanti Neurons for Secure Access version
    Run 'dp get system.version' or access the admin dashboard under System > Configuration > System Management > System Information
    Affected if Version is < 22.8 or exactly 22.8 (version 22.8R1.4 and later are fixed)

If the installed product version matches any of the affected version ranges listed above, the environment is vulnerable to symlink-based arbitrary file read by local authenticated users.

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: upgrade Ivanti Connect Secure to 22.7R2.8/22.8R2 or later, Policy Secure to 22.7R1.5 or later, ZTA Gateway to 22.8R2.3-723 or later, and Neurons for Secure Access to 22.8R1.4 or later.

Recommended fix High confidence

Product-specific: 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 specific Ivanti product in use (Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access)
  2. 2. Determine the current installed version by checking the system administration console or using the CLI command 'show version'
  3. 3. For Connect Secure: upgrade to version 22.7R2.8 or 22.8R2 or later
  4. 4. For Policy Secure: upgrade to version 22.7R1.5 or later
  5. 5. For Zero Trust Access Gateway: upgrade to version 22.8R2.3-723 or later
  6. 6. For Neurons for Secure Access: upgrade to version 22.8R1.4 or later
  7. 7. After upgrade, verify the new version is installed using 'show version'
  8. 8. Test that the symbolic link handling now properly validates targets before following links
Caveat Standard upgrade considerations apply - review release notes for any configuration changes between versions; test in staging environment before production deployment

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5468 — 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-5468 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