Service interruption via null ownership guard
Published Apr 17, 2026 · Updated Apr 17, 2026
Incorrect authorization in OpenZiti zrok before 2.0.1 allows remote authenticated users to delete a global frontend via the unaccess API. The unaccessHandler.Handle ownership guard treats a NULL frontend environment_id as a reason to skip ownership verification, then deletes the record. Exploitation requires a valid account, an owned environment ID, and knowledge of a global frontend token; deletion interrupts every public share routed through that frontend.
Summary
What happened
Incorrect authorization in OpenZiti zrok before 2.0.1 allows remote authenticated users to delete a global frontend via the unaccess API. The unaccessHandler.Handle ownership guard treats a NULL frontend environment_id as a reason to skip ownership verification, then deletes the record. Exploitation requires a valid account, an owned environment ID, and knowledge of a global frontend token; deletion interrupts every public share routed through that frontend.
The record
- CVE
- CVE-2026-40304
- Published
- Apr 17, 2026
- Updated
- Apr 17, 2026
- Vendor
- OpenZiti
- Product
- zrok
- Classifications
- CWE-863, CWE-284, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 2026CVE publishedPublication date reported by the CVE source.
- Apr 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo