# CVE-2026-45576: zrok copy writes attacker-controlled WebDAV paths outside the destination root

> Attackers can write files outside the destination root via crafted WebDAV paths in zrok copy operations, requiring an upgrade to mitigate.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-c656-jcx2-7pqj, GO-2026-5315

## What is CVE-2026-45576?

CVE-2026-45576 is a high-severity path traversal vulnerability in openziti zrok, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

zrok is software for sharing web services, files, and network resources. From 0.4.23 until 2.0.3, `zrok2 copy` stores attacker-controlled WebDAV or zrok drive paths such as /../outside.txt in the source inventory and passes them to FilesystemTarget.WriteStream, allowing the sync pipeline to write files outside the selected local filesystem destination root. This issue is fixed in version 2.0.3.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-45576?

6 open source packages ship an affected version, including github.com/openziti/zrok and github.com/openziti/zrok/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openziti/zrok` | Go | From 0.4.23 | None |
| `github.com/openziti/zrok` | Go | From 0.4.23 to 1.1.11 | None |
| `github.com/openziti/zrok` | Go | From 0.4.23 to 1.1.11 | None |
| `github.com/openziti/zrok/v2` | Go | All versions | 2.0.3 |
| `github.com/openziti/zrok/v2` | Go | All versions | 2.0.3 |
| `github.com/openziti/zrok/v2` | Go | All versions | 2.0.3 |

Products: Netfoundry Zrok.

## How do I fix CVE-2026-45576?

Upgrade to a fixed version.

## Is CVE-2026-45576 being exploited?

There is no known exploitation of CVE-2026-45576 in the wild and no public exploit code.

## Other vulnerabilities in openziti zrok

- [CVE-2026-45568](https://insights.sbomify.com/CVE-2026-45568/): zrok Python ProxyShare can be used as an SSRF proxy through absolute URL paths (critical 9.9)
- [CVE-2026-42275](https://insights.sbomify.com/CVE-2026-42275/): zrok: WebDAV drive backend follows symlinks outside DriveRoot, enabling host filesystem read/write (high 8.7)
- [CVE-2026-40303](https://insights.sbomify.com/CVE-2026-40303/): zrok allows unauthenticated DoS via unbounded memory allocation in striped session cookie parsing (high 7.5)
- [CVE-2026-40302](https://insights.sbomify.com/CVE-2026-40302/): zrok has reflected XSS in GitHub OAuth callback via unsanitized refreshInterval error rendering (medium 6.1)
- [CVE-2026-40304](https://insights.sbomify.com/CVE-2026-40304/): zrok's broken ownership check in DELETE /api/v2/unaccess allows non-admin to delete global frontend records (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45576 and fix it if it is affected.

What it is: CVE-2026-45576 is a high-severity path traversal vulnerability in openziti zrok, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-45576 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/openziti/zrok (Go): affected from 0.4.23; no fix listed
- github.com/openziti/zrok (Go): affected from 0.4.23 up to 1.1.11; no fix listed
- github.com/openziti/zrok (Go): affected from 0.4.23 up to 1.1.11; no fix listed
- github.com/openziti/zrok/v2 (Go): affected all versions; fixed in 2.0.3
- github.com/openziti/zrok/v2 (Go): affected all versions; fixed in 2.0.3
- github.com/openziti/zrok/v2 (Go): affected all versions; fixed in 2.0.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45576/ (Markdown: https://insights.sbomify.com/CVE-2026-45576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45576
- OSV: https://osv.dev/vulnerability/CVE-2026-45576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45576/
Summaries are generated and may contain mistakes; the official description above is the record.