# rok Python ProxyShare can be used as an SSRF proxy through absolute URL paths

Advisory record · `GHSA-jh67-hwqw-m5r7`

- **Identifiers:** `GHSA-jh67-hwqw-m5r7` · `CVE-2026-45568` · `PYSEC-2026-577`
- **State:** Confirmed
- **Severity:** CVSS 9.9 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 29 Jun 2026
- **Updated:** 1 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.9: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `zrok` (PyPI): affected `>=0.4.47, <=1.1.11`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The zrok Python package, versions >=0.4.47 and <=1.1.11, has a server-side request forgery flaw in its ProxyShare SDK. The proxy builds its outbound URL with urljoin, so a request carrying an absolute URL in the path makes the server fetch that URL instead of the configured target. A remote user who can reach a share can use it to reach internal hosts and return their responses. The source lists no fixed version and no workaround.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.9 Critical, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0054, the 46th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jun 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-jh67-hwqw-m5r7](https://github.com/advisories/GHSA-jh67-hwqw-m5r7)
- [OSV: GHSA-jh67-hwqw-m5r7](https://osv.dev/vulnerability/GHSA-jh67-hwqw-m5r7)
- <https://github.com/openziti/zrok/security/advisories/GHSA-jh67-hwqw-m5r7>
- <https://github.com/openziti/zrok>
- <https://pypi.org/project/zrok>
- <https://github.com/advisories/GHSA-jh67-hwqw-m5r7>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-45568>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jh67-hwqw-m5r7>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jh67-hwqw-m5r7/>. Everything for agents: <https://agentprime.io/llms.txt>.
