CVE-2025-55145
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 to hijack existing HTML5 connections.
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 check in Ivanti Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access allows an authenticated remote attacker to hijack existing HTML5 connections (likely RDP/VNC sessions) by leveraging the lack of proper authorization validation on established sessions.
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.8= 22.8< 22.7= 22.7< 22.7= 22.7= 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L
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 deployed Ivanti productDetermine which Ivanti security product is running in your environment (Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access). This is typically visible in the product name or admin interface.Affected if The product is any of the four affected: Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access.
-
Check the installed versionLocate the version number of your Ivanti product through the admin console, system information page, or command line interface if available. Compare this version against the affected ranges: Neurons For Secure Access versions < 22.8 or = 22.8; Connect Secure versions < 22.7 or = 22.7; Policy Secure versions < 22.7 or = 22.7; Zero Trust Access Gateway version = 22.8.Affected if Your installed version falls within any of these affected ranges.
-
Verify HTML5 connection feature is in useCheck if HTML5 connections (remote access via HTML5 portals) are enabled or commonly used in your deployment. This is typically configurable in the product settings or visible in active connection logs.Affected if HTML5 connections are enabled and users establish sessions through this feature.
-
Inspect session management configurationReview the session management settings in your Ivanti product to confirm that session tokens or session identifiers are present and can be intercepted or manipulated. Look for active sessions in the admin interface or session logs.Affected if Active HTML5 sessions exist in the environment and session tokens are accessible without proper authorization verification.
-
Review access logs for suspicious session behaviorExamine authentication and session logs for any unauthorized session access patterns, particularly where a user attempts to access an existing session belonging to another user.Affected if Logs show successful session takeover attempts or unexpected session binding behavior.
You are affected if you are running any of the four products (Connect Secure, Policy Secure, ZTA Gateway, or Neurons for Secure Access) within the specified version ranges AND HTML5 connection sessions are active in your environment.
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 the 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 (fixes were deployed 02-Aug-2025).
Ivanti Connect Secure: 22.7R2.9 or 22.8R2; Ivanti Policy Secure: 22.7R1.6; Ivanti ZTA Gateway: 2.8R2.3-723; Ivanti Neurons for Secure Access: 22.8R1.4
- Identify the specific Ivanti product in use (Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access)
- Determine the current installed version from the admin console or system information
- For Ivanti Connect Secure: upgrade to version 22.7R2.9 or 22.8R2 or later
- For Ivanti Policy Secure: upgrade to version 22.7R1.6 or later
- For Ivanti Zero Trust Access Gateway: upgrade to version 2.8R2.3-723 or later
- For Ivanti Neurons for Secure Access: upgrade to version 22.8R1.4 or later
- After upgrade, verify the HTML5 connection hijacking vulnerability is resolved by testing existing sessions
- Confirm the fix deployment date of 02-Aug-2025 is reflected in the system
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55145 — 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-55145 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