# CVE-2026-45568: zrok Python ProxyShare can be used as an SSRF proxy through absolute URL paths

> Attackers can exploit the zrok Python SDK ProxyShare to perform Server-Side Request Forgery by manipulating URL paths to access internal resources.

- **Severity:** Critical 9.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-jh67-hwqw-m5r7, PYSEC-2026-577

## What is CVE-2026-45568?

CVE-2026-45568 is a critical server-side request forgery vulnerability in openziti zrok, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

zrok is software for sharing web services, files, and network resources. Prior to 2.0.3, zrok's Python SDK ProxyShare Flask proxy route accepts an absolute URL in the request path and passes it to urllib.parse.urljoin, allowing the requested path to replace the configured target host and causing requests.request to return a server-side response from an attacker-chosen URL. 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-45568?

3 open source packages ship an affected version, including zrok. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zrok` | PyPI | From 0.4.47 to 1.1.11 | None |
| `zrok` | PyPI | From 0.4.47 to 1.1.11 | None |
| `zrok` | PyPI | From 0.4.47 to 1.1.11 | None |

Products: Netfoundry Zrok.

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

No fix has been published for CVE-2026-45568 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45568 being exploited?

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

## Other vulnerabilities in openziti zrok

- [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-45576](https://insights.sbomify.com/CVE-2026-45576/): zrok copy writes attacker-controlled WebDAV paths outside the destination root (high 8.3)
- [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-45568 and fix it if it is affected.

What it is: CVE-2026-45568 is a critical server-side request forgery vulnerability in openziti zrok, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45568 in the wild and no public exploit code.

Affected packages and fixed versions:
- zrok (PyPI): affected from 0.4.47 up to 1.1.11; no fix listed
- zrok (PyPI): affected from 0.4.47 up to 1.1.11; no fix listed
- zrok (PyPI): affected from 0.4.47 up to 1.1.11; no fix listed

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-45568/ (Markdown: https://insights.sbomify.com/CVE-2026-45568/index.md)
```

## Sources

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

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