dbcve.org
OpenzitiApplication

CVE-2025-27501

HIGH · 8.6 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to 3.7.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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
OpenZiti is a free and open source project focused on bringing zero trust to any application. An endpoint on the admin panel can be accessed without any form of authentication. This endpoint accepts a user-supplied URL parameter to connect to an OpenZiti Controller and performs a server-side request, resulting in a potential Server-Side Request Forgery (SSRF) vulnerability. The fixed version has moved the request to the external controller from the server side to the client side, thereby eliminating the identity of the node from being used to gain any additional permissions. This vulnerability is fixed in 3.7.1.

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

An unauthenticated endpoint in the OpenZiti admin panel accepts a user-supplied URL parameter to connect to an OpenZiti Controller and performs a server-side request, resulting in Server-Side Request Forgery (SSRF). The server's identity can be leveraged to gain additional permissions when connecting to external controllers.

MitigationUpgrade to OpenZiti version 3.7.1 or later, which moves the external controller request from server-side to client-side, eliminating the SSRF vector.

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
OpenzitiApplication
Affected:< 3.7.1

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenZiti controller version
    Run 'ziti-controller version' or check the installed package version using your system package manager (dpkg, rpm, etc.)
    Affected if The installed version is lower than 3.7.1 (e.g., 3.6.x, 3.5.x, etc.)
  2. Locate the Ziti Admin UI configuration
    Examine the Ziti controller configuration file (typically under /etc/ziti or the configured config directory) for the 'admin' or 'ui' section that defines the admin panel bind address
    Affected if The admin UI is bound to a network interface accessible from untrusted networks (0.0.0.0 or public IP) rather than localhost only
  3. Verify admin UI network exposure
    Check listening ports on the system (netstat -tlnp or ss -tlnp) and identify if port 8441 (default Ziti Admin UI port) or the configured admin UI port is bound to a public IP
    Affected if The admin UI port is listening on 0.0.0.0 or an external IP address, making it accessible remotely
  4. Confirm unauthenticated access is possible
    Attempt to access the admin UI endpoint without authentication from an external system (e.g., curl http://<host>:8441)
    Affected if The endpoint responds without requiring authentication, indicating the panel is exposed without proper access controls

You are affected if the OpenZiti controller version is below 3.7.1 AND the Ziti Admin UI is accessible over the network without authentication.

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 3.7.1 or later
Fixed in 3.7.1
Interim mitigation

Upgrade to OpenZiti version 3.7.1 or later, which moves the external controller request from server-side to client-side, eliminating the SSRF vector.

Recommended fix High confidence

3.7.1

  1. 1. Back up your current OpenZiti configuration and data directories
  2. 2. Download OpenZiti version 3.7.1 from the official GitHub releases or package repository
  3. 3. Stop the running OpenZiti services
  4. 4. Install or extract version 3.7.1 following standard installation procedures
  5. 5. Restore your configuration from the backup
  6. 6. Start the OpenZiti services
  7. 7. Verify the upgrade by checking that the admin panel endpoint no longer performs server-side requests

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openziti Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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