rok Python ProxyShare can be used as an SSRF proxy through absolute URL paths
CVE-2026-45568GHSA-jh67-hwqw-m5r7
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI zrok
- Affected
- >= 0.4.47, <= 1.1.11
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jh67-hwqw-m5r7 lists affected ranges: PyPI zrok >=0.4.47 <=1.1.11
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-jh67-hwqw-m5r7 lists affected ranges: PyPI zrok >=0.4.47 <=1.1.11
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 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 · score source
- EPSS
- CVE-2026-45568: 0.54% estimated exploitation activity in the next 30 days; percentile 45.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Alice exposes a Python SDK ProxyShare with a fixed target URL. Bob sends a request to the share with an absolute URL in the path. The Flask handler passes that path to urllib.parse.urljoin, which replaces Alice's configured target host with Bob's host and returns the server-side response to Bob. Details The Python SDK proxy route accepts every path under the share: It constructs the outbound URL with urljoin and then sends the request: When path is http://127.0.0.1:19190/metadata, urljoin(self.target, path) returns http://127.0.0.1:19190/metadata. The proxy sends the request to Bob's chosen URL rather than Alice's target.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 4 · amended ·
Amended from ghsa record GHSA-jh67-hwqw-m5r7
- Revision 3 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 2 · amended ·
Amended from osv record GHSA-jh67-hwqw-m5r7
- Revision 1 · created ·
Published from ghsa record GHSA-jh67-hwqw-m5r7
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-45568 Advisory: rok Python ProxyShare can be used as an SSRF proxy through absolute URL paths IDs: CVE-2026-45568, GHSA-jh67-hwqw-m5r7 Record: https://patchnext.com/advisories/cve-2026-45568 (revision 4, source checked 26 Oct 2026, 13:41 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI zrok: affected >= 0.4.47, <= 1.1.11 ## Suggested inspection (read-only) - `python -m pip show zrok`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on zrok. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-jh67-hwqw-m5r7 (GitHub-reviewed advisory GHSA-jh67-hwqw-m5r7 lists affected ranges: PyPI zrok >=0.4.47 <=1.1.11) - Verified: https://osv.dev/vulnerability/GHSA-jh67-hwqw-m5r7 (OSV record GHSA-jh67-hwqw-m5r7 lists affected ranges: PyPI zrok >=0.4.47 <=1.1.11) Commands are suggestions: review each one before running it.
Loading voting…