Quick answers
- Is CVE-2026-45576 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45576 being exploited in the wild.
- How severe is CVE-2026-45576?
- High severity, with a CVSS score of 4, published 16 July 2026.
- Which products and versions are affected?
- github.com/openziti/zrok (Go) >= 0.4.23, <= 1.1.11, SEMVER:introduced=0.4.23, SEMVER:introduced=0.4.23,last_affected=1.1.11; github.com/openziti/zrok/v2 (Go) < 2.0.3, SEMVER:introduced=0,fixed=2.0.3; OpenZiti Zrok < 2.0.3, >= 0.4.23, < 2.0.3.
- Is there a fix for CVE-2026-45576?
- Yes. github.com/openziti/zrok/v2 (Go): upgrade to 2.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45576 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45576?
- Check whether you run github.com/openziti/zrok (Go), github.com/openziti/zrok/v2 (Go) or OpenZiti 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.3 or later
go get github.com/openziti/zrok/v2@v2.0.3
Technical details
A path traversal vulnerability (CWE-22) exists in the 'zrok2 copy' command of zrok. The issue stems from the application failing to sanitize WebDAV or zrok drive paths (e.g., using '/../') before passing them to the FilesystemTarget.WriteStream function. An attacker who controls a source share can provide malicious paths that the sync pipeline will use to write, remove, or modify files outside the user's selected local destination directory. Exploitation requires a user to initiate a copy operation from an attacker-controlled share. The vulnerability is fixed in version 2.0.3 by implementing root-confinement for local drive sync operations.
Affected products
- openziti zrok >= 0.4.23, < 2.0.3
Identifiers
- CVE-2026-45576
- GHSA-c656-jcx2-7pqj
- GO-2026-5315
Timeline
- 2026-05-07: patched: Fix committed and version 2.0.3 released.
- 2026-05-13: advisory: GitHub Security Advisory published.
- 2026-07-16: disclosed: CVE-2026-45576 published to NVD.