HIGH 8.8

CVE-2026-58165: OpenZiti Privilege Escalation via Enrollment Authorization Bypass

OpenZiti, a zero-trust networking platform, contains a privilege escalation flaw that allows authenticated users with enrollment management permissions to impersonate administrators. An attacker with these limited permissions can trick the system into issuing administrative credentials, effectively hijacking the entire network controller and gaining full control over the zero-trust overlay. The vulnerability exists because the system fails to verify that an enrollment request comes from someone authorized to act on behalf of the target identity.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.8 HIGH · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-862
Affected products
0 configuration(s)
Published / Modified
2026-06-30 / 2026-07-14

NVD description (verbatim)

OpenZiti through 2.0.0, fixed in commit 3027fdf, contains a privilege escalation vulnerability that allows authenticated non-admin identities with fine-grained enrollment management permissions to create enrollments for any identity, including the default administrator, because the ApplyCreate function in controller/model/enrollment_manager.go verifies only that the target identity exists without performing authorization checks binding the caller to the target identity. Attackers can redeem the resulting one-time token through the unauthenticated client API enrollment endpoint to obtain a client certificate authenticating as the targeted admin identity, yielding full administrative control of the controller and the zero-trust overlay it manages.

4 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-58165 is a post-authentication privilege escalation in OpenZiti through version 2.0.0, stemming from insufficient authorization validation in the ApplyCreate function within controller/model/enrollment_manager.go. The enrollment manager verifies only that a target identity exists, not that the requesting principal has authorization to create enrollments for that target. An authenticated attacker holding fine-grained enrollment management permissions can invoke ApplyCreate to generate a one-time enrollment token for any identity, including the default administrator. The attacker then redeems this token through the unauthenticated client enrollment API endpoint, obtaining a valid client certificate bound to the target admin identity. This certificate authenticates the attacker to the controller with full administrative privileges. The fix, applied in commit 3027fdf, implements proper authorization checks binding the caller's permissions to the requested enrollment target.

Business impact

Compromise of the OpenZiti controller translates directly to control of the entire zero-trust overlay network. An insider or compromised low-privilege user can escalate to administrator, gaining the ability to modify access policies, enroll malicious identities, inspect encrypted traffic metadata, revoke legitimate access, or inject rogue endpoints. For organizations relying on OpenZiti to enforce network segmentation and secure remote access, this vulnerability undermines the security model's core assumption that administrative controls prevent unauthorized changes to trust relationships.

Affected systems

OpenZiti versions through 2.0.0 are affected. The vulnerability requires an authenticated identity with enrollment management permissions on the controller; however, depending on how OpenZiti is deployed, enrollment permissions may be delegated broadly. Systems that have not applied the fix in commit 3027fdf remain vulnerable.

Exploitability

Exploitability is moderate-to-high. The attack requires prior authentication and specific fine-grained permissions (enrollment management), narrowing the attacker pool to trusted insiders, compromised service accounts, or accounts obtained through credential theft. However, once an attacker holds these permissions—which may be granted to security teams, identity administrators, or automated provisioning services—the escalation path is straightforward and requires no user interaction or complex manipulation. The one-time token redemption occurs through an unauthenticated endpoint, meaning no further authentication is needed to complete the takeover.

Remediation

Organizations must upgrade to a version of OpenZiti containing the authorization fix (verify against the vendor advisory for the exact patched version number corresponding to commit 3027fdf). Interim compensating controls include strictly limiting enrollment management permissions to essential administrators only, implementing strong identity federation and MFA on privileged accounts, monitoring enrollment token issuance and certificate creation events, and reviewing audit logs for suspicious enrollment requests. Assume breach: if this vulnerability was exploitable in your environment, rotate all administrator credentials and review audit logs for unauthorized enrollments or certificate issuance.

Patch guidance

Apply the OpenZiti version containing commit 3027fdf. Verify the exact version number and availability through the vendor's security advisory and release notes. Follow standard change management procedures; the controller should be updated in a controlled maintenance window, as all enrolled identities depend on it. After patching, validate that the authorization checks are enforced by testing that non-admin identities can no longer create enrollments for other identities.

Detection guidance

Monitor controller logs and audit trails for: (1) enrollment creation requests where the requesting identity differs from the target identity, especially requests targeting administrative accounts; (2) rapid or unusual patterns of token generation; (3) certificate issuance events tied to unexpected identities; (4) access by low-privilege accounts to enrollment management APIs. Implement alerting on any enrollment token redemption for the default administrator or other high-value identities. Network detection is limited because the final escalation uses valid certificates, but anomalous policy changes or access patterns post-compromise may reveal the attack.

Why prioritize this

This vulnerability should be prioritized immediately if OpenZiti is deployed in your environment. The CVSS 3.1 score of 8.8 (HIGH) reflects the severity: it requires authentication but grants full administrative control. In zero-trust architectures, the controller is the trust anchor; its compromise is equivalent to compromising Active Directory or a root CA. Even organizations with strong perimeter defenses depend on OpenZiti's policy engine to enforce least-privilege access. A single malicious or compromised identity with enrollment permissions can bypass all downstream security controls.

Risk score, explained

The CVSS 3.1 score of 8.8 reflects a HIGH severity rating. The vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates network-accessible exploitation (AV:N), low attack complexity (AC:L), requirement for low-level privileges (PR:L), no user interaction (UI:N), and impact on confidentiality, integrity, and availability within the same security boundary (S:U/C:H/I:H/A:H). The requirement for prior authentication and specific permissions prevents a score above 9.0, but the direct path to administrator control and full system compromise justifies the high rating.

Frequently asked questions

Can this be exploited by unauthenticated users?

No. The attacker must first authenticate to the OpenZiti controller and hold fine-grained enrollment management permissions. However, once authenticated with those permissions, the escalation to admin requires no further authentication steps.

What is the practical impact if our OpenZiti enrollment permissions are tightly restricted?

If only a very small number of administrators can create enrollments, the attack surface is narrow. However, if enrollment permissions are delegated to identity teams, provisioning services, or help desk roles (common in larger deployments), the risk increases significantly. Audit your current permission assignments to assess your specific risk.

Can we detect if this vulnerability was exploited in our logs?

Possibly, through careful audit log analysis. Look for enrollment token creation targeting administrative identities, especially from lower-privileged accounts, and certificate issuance events that followed unusual token redemptions. However, if the attacker obtained administrative credentials, they may attempt to cover their tracks by modifying or deleting logs.

Does this affect the zero-trust identities enrolled in the overlay, or just the controller?

The vulnerability compromises the controller itself, which is the trust anchor and policy engine. Once the controller is compromised, an attacker can manipulate any policy, enroll malicious identities, or revoke legitimate ones—effectively breaking the trust model for all enrolled endpoints and services.

This analysis is based on the published CVE description and CVSS vector. Specific affected product versions and patched versions are subject to the vendor's official advisory; verify all remediation steps with the OpenZiti project's security announcements before deployment. This vulnerability requires authentication and specific permissions; however, the ease of escalation once those conditions are met makes it a critical priority. Organizations should assume breach and conduct forensic review of audit logs if OpenZiti deployments were running vulnerable versions. No exploit code or weaponized proof-of-concept is provided or endorsed. Source: NVD (public-domain), retrieved 2026-08-09. Analysis generated by SEC.co (claude-haiku-4-5).