CVE-2025-55141
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 · uneditedMissing 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 confidenceMissing authorization in multiple Ivanti products allows authenticated read-only admin users to modify authentication settings, bypassing intended role-based access controls. This is a privilege escalation vulnerability where the read-only restriction is not properly enforced on authentication-related configuration endpoints.
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< 22.7= 22.7< 22.7= 22.7= 22.8< 22.8= 22.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Ivanti product and versionAccess the admin console or use system information commands to determine which Ivanti product is installed (Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access) and note the exact version numberAffected if The product version falls within the affected ranges: Connect Secure or Policy Secure < 22.7 or = 22.7; Zero Trust Access Gateway = 22.8; Neurons for Secure Access < 22.8 or = 22.8
-
Review user role configurationsAccess the admin user management section and list all defined administrator accounts along with their assigned roles, specifically noting which accounts have read-only administrator privilegesAffected if Read-only administrator accounts exist in the system
-
Audit authentication settings access controlsExamine the authentication configuration panels and permissions settings to determine whether read-only administrator accounts have been granted write access to authentication-related settings such as user authentication methods, LDAP integration, or authentication policiesAffected if Read-only administrator roles are permitted to modify authentication settings or authentication policies beyond their intended read-only scope
-
Review system logs for privilege escalation indicatorsSearch authentication and admin audit logs for events where read-only administrator accounts modified authentication configurations, changed user roles, or altered authentication policiesAffected if Logs show read-only admin accounts making changes to authentication settings or user role assignments
A user is affected if they are running one of the listed Ivanti product versions AND have read-only administrator accounts configured, as those accounts can potentially modify authentication settings beyond their intended permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped22.722.8
Apply vendor patches (22.7R2.9/22.8R2 for Connect Secure, 22.7R1.6 for Policy Secure, 2.8R2.3-723 for ZTA Gateway, 22.8R1.4 for Neurons) deployed August 2, 2025. Review admin user role assignments as part of remediation.
For Connect Secure: upgrade to 22.7R2.9 or 22.8R2 | For Policy Secure: upgrade to 22.7R1.6 | For ZTA Gateway: upgrade to 2.8R2.3-723 | For Neurons for Secure Access: upgrade to 22.8R1.4
- 1. Identify the currently installed Ivanti product version (Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access)
- 2. Navigate to the Ivanti customer portal or download center
- 3. Download the appropriate fixed release version for your product: For Connect Secure: upgrade to 22.7R2.9 or later, or 22.8R2 or later | For Policy Secure: upgrade to 22.7R1.6 or later | For Zero Trust Access Gateway: upgrade to 2.8R2.3-723 or later | For Neurons for Secure Access: upgrade to 22.8R1.4 or later
- 4. Review upgrade prerequisites and release notes in the Ivanti documentation
- 5. Schedule a maintenance window as upgrades may require downtime
- 6. Back up current configuration before proceeding
- 7. Perform the upgrade following Ivanti's standard upgrade procedures
- 8. After upgrade, verify the version and confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55141 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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