dbcve.org
Connect SecureApplication · Ivanti

CVE-2025-55142

HIGH · 8.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 22.7 / 22.8 or later.
See remediation →
94/100
Remediation priority · Urgent
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 authentication related 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 vulnerability in Ivanti Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access allows authenticated read-only admin users to bypass authorization and configure authentication-related settings they should not have access to, effectively enabling privilege escalation.

MitigationApply vendor-supplied patches (August 2025) by upgrading to 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, and audit admin accounts for unauthorized configuration changes.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the installed product and version
    Access the admin console or check system information to determine which Ivanti product is running (Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access) and note the exact version number.
    Affected if The installed version is Connect Secure or Policy Secure < 22.7 or = 22.7, ZTA Gateway = 22.8, or Neurons for Secure Access < 22.8 or = 22.8
  2. Verify if read-only admin accounts exist
    Review the admin user management section of the console to list all configured administrator accounts and identify any that are assigned read-only privileges.
    Affected if Read-only admin accounts exist in the system (the vulnerability allows these accounts to bypass authorization)
  3. Review authentication-related configuration for unauthorized changes
    Examine authentication settings, LDAP/AD integrations, RADIUS configurations, certificate settings, and user authentication policies. Compare current settings against known baselines or documentation.
    Affected if Settings have been modified that exceed what read-only admin accounts should be able to change, indicating successful exploitation
  4. Audit admin activity logs for privilege escalation indicators
    Search authentication and admin activity logs for actions performed by read-only admin accounts that modified system configuration, particularly changes to authentication settings, user roles, or policy modifications.
    Affected if Logs show read-only admin accounts making configuration changes they should not be permitted to make

A user is affected if the installed product version falls within the vulnerable ranges AND read-only admin accounts exist and may have modified authentication settings without proper authorization.

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 (August 2025) by upgrading to 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, and audit admin accounts for unauthorized configuration changes.

Recommended fix High confidence

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

  1. 1. Identify the specific Ivanti product and current version (Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access)
  2. 2. For Connect Secure: upgrade to version 22.7R2.9 or 22.8R2 or later
  3. 3. For Policy Secure: upgrade to version 22.7R1.6 or later
  4. 4. For Zero Trust Access Gateway: upgrade to version 2.8R2.3-723 or later
  5. 5. For Neurons for Secure Access: upgrade to version 22.8R1.4 or later
  6. 6. Verify the upgrade was successful and the version matches a fixed release

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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