Skip to content
OpenAdvisories
Medium · 5.3 CVE-2026-40304 EUVD-2026-23551GHSA-3jpj-v3xr-5h6gGO-2026-5090

zrok's broken ownership check in DELETE /api/v2/unaccess allows non-admin to delete global frontend records

Published Apr 17, 2026 · Updated Apr 20, 2026 · Assigned by GitHub_M

Description

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.

Affected products

VendorProductAffectedFixed
openziti zrok < 2.0.1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
openSUSE Leap 16.0 govulncheck-vulndb 0.0.20260723T184607-160000.1.1 openSUSE-SU-2026:21483-1

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/openziti/zrok <= 1.1.11 — GHSA-3jpj-v3xr-5h6g
Go github.com/openziti/zrok all versions — GO-2026-5090
Go github.com/openziti/zrok/v2 < 2.0.1 2.0.1 GHSA-3jpj-v3xr-5h6g

Advisories 1

References