dbcve.org
Connect SecureApplication · Ivanti

CVE-2025-55148

HIGH · 7.6 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 22.7 / 22.8 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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
Missing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6, Ivanti ZTA Gateway before 2.8R2.3-723 and Ivanti Neurons for Secure Access before 22.8R1.4 (Fix deployed on 02-Aug-2025) allows a remote authenticated attacker with read-only admin privileges to configure restricted settings.

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

Missing authorization in multiple Ivanti products (Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access) allows authenticated read-only admin users to bypass restrictions and configure settings that should only be modifiable by full administrators. This authorization bypass enables privilege escalation within the application.

MitigationApply vendor-supplied patches: Update Ivanti Connect Secure to 22.7R2.9/22.8R2, Policy Secure to 22.7R1.6, ZTA Gateway to 2.8R2.3-723, and Neurons for Secure Access to 22.8R1.4 (all released August 2, 2025).

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 and version
    Access the admin UI or use CLI command (e.g., 'show version' or similar) to determine which Ivanti product is deployed and its exact version number
    Affected if Version matches: Connect Secure < 22.7 or = 22.7, Policy Secure < 22.7 or = 22.7, ZTA Gateway = 22.8, or Neurons for Secure Access < 22.8 or = 22.8
  2. Confirm presence of read-only admin accounts
    In the admin UI, navigate to the user administration section and list accounts with read-only or restricted administrator roles
    Affected if Any read-only admin accounts exist in the system
  3. Review admin role permissions for read-only users
    Examine the permission settings for read-only admin roles in the admin UI under System Administration > Administrators > Roles to verify they should be restricted from modifying configuration
    Affected if Read-only admin roles exist and are intended to be restricted from configuration changes
  4. Check configuration modification audit logs
    Review system logs or audit logs for instances where read-only admin accounts modified settings that should require full administrator privileges
    Affected if Any configuration changes were performed by read-only admin accounts when they should not have been permitted

The environment is affected if any Ivanti product version matches the affected ranges AND read-only admin accounts exist that could have bypassed authorization to modify settings.

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 vendor-supplied patches: Update Ivanti Connect Secure to 22.7R2.9/22.8R2, Policy Secure to 22.7R1.6, ZTA Gateway to 2.8R2.3-723, and Neurons for Secure Access to 22.8R1.4 (all released August 2, 2025).

Recommended fix High confidence

Upgrade to the appropriate fixed release: Connect Secure 22.7R2.9/22.8R2+, Policy Secure 22.7R1.6+, ZTA Gateway 2.8R2.3-723+, or 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 from the admin console or system information
  3. 3. For Connect Secure: Upgrade to version 22.7R2.9 or 22.8R2 or later
  4. 4. For Policy Secure: Upgrade to version 22.7R1.6 or later
  5. 5. For Zero Trust Access Gateway: Upgrade to version 2.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 fix by confirming read-only admin accounts can no longer modify restricted settings
  8. 8. Review admin role permissions to ensure least-privilege principles are applied
Caveat Review release notes for potential changes to admin role configurations and test in staging 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
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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