CVE-2025-55139
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 · uneditedSSRF 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 admin privileges to enumerate internal services.
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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in the web management interfaces of Ivanti Connect Secure, Policy Secure, ZTA Gateway, and Neurons for Secure Access. An attacker with authenticated admin privileges can send crafted requests through the vulnerable server to enumerate internal services, potentially revealing internal infrastructure details.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify product and versionLog into the web admin console and navigate to the System/Dashboard or System > Management > Software page to view the installed version. Alternatively, check the system banner or about page.Affected if The product is Ivanti Connect Secure version < 22.7 or = 22.7; Ivanti Policy Secure version < 22.7 or = 22.7; Ivanti Zero Trust Access Gateway version = 22.8; or Ivanti Neurons for Secure Access version < 22.8 or = 22.8
-
Verify web management interface is enabledConfirm the admin web interface is accessible on the appliance. Check if HTTPS admin access is enabled in the system configuration.Affected if The web management interface is exposed and accessible (the vulnerability exists in this component)
-
Check admin account configurationReview admin user accounts in System > Administrators or the equivalent section. Verify which accounts have admin-level privileges.Affected if Any authenticated admin-level account exists in the system (required for exploitation)
-
Audit admin access logs for internal enumerationReview system logs, especially admin audit logs and access logs, for patterns of requests to internal IP ranges (10.x.x.x, 192.168.x.x, 172.16-31.x.x) or internal hostnames that did not originate from trusted internal sources.Affected if Logs show requests to internal services from the appliance that were initiated through the admin interface
-
Check for suspicious outbound connectionsReview network connection logs or firewall logs for unusual outbound connections from the appliance to internal infrastructure that correspond to admin login sessions.Affected if The appliance has initiated connections to internal services during periods when admin users were logged in
You are affected if you are running any of the listed product versions with the admin web interface enabled and have admin accounts configured.
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 fix deployed on August 2, 2025 by upgrading to Ivanti 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 or later. Limit admin access to trusted networks and monitor for suspicious internal service enumeration patterns.
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. Identify the specific Ivanti product in use (Connect Secure, Policy Secure, Zero Trust Access Gateway, or Neurons for Secure Access)
- 2. Check the current installed version using the administrative interface or system diagnostics
- 3. For Connect Secure: Upgrade to version 22.7R2.9 or 22.8R2 or later
- 4. For Policy Secure: Upgrade to version 22.7R1.6 or later
- 5. For Zero Trust Access Gateway: Upgrade to version 2.8R2.3-723 or later
- 6. For Neurons For Secure Access: Upgrade to version 22.8R1.4 or later
- 7. After upgrade, verify the SSRF vulnerability is remediated by confirming internal service enumeration is no longer possible
- 8. Review admin privilege assignments and follow least-privilege principles
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.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-55139 — 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-55139 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