CVE-2026-40304: zrok: Broken ownership check in DELETE /api/v2/unaccess allows non-admin to delete global frontend records
CVE-2026-40304 · Severity: medium · CVSS 5.3 · Published 2026-04-17
zrok is software for sharing web services, files, and network resources. Prior to version 2.0.1, the unaccess handler (controller/unaccess.go) contains a logical error in its ownership guard: when a frontend record has environment_id = NULL (the marker for admin-created global frontends), the condition short-circuits to false and allows the deletion to proceed without any ownership verification. A non-admin user who knows a global frontend token can call DELETE /api/v2/unaccess with any of their own environment IDs and permanently delete the global frontend, taking down all public shares routed through it. Version 2.0.1 patches the issue.
Yes. github.com/openziti/zrok/v2 (Go): upgrade to 2.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-40304?
Check whether you run github.com/openziti/zrok (Go), github.com/openziti/zrok/v2 (Go) or Netfoundry Zrok at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
github.com/openziti/zrok/v2 (Go): upgrade to 2.0.1 or later