← Back
CVE-2026-45568
critical
CVSS 9.1
Path Traversal in zrok (CVE-2026-45568)
Summary
path traversal in zrok (CVE-2026-45568). Confidential information can be exposed externally. Exploitable via ``ProxyShare``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45568** has been found in zrok.
Attackers can target a specific entry point like ``ProxyShare`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "zrok CVE-2026-45568" on the vendor's site.
CVE-2026-45568 (zrok) — CWE-22 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `ProxyShare` / `urllib.parse.urljoin` / `urljoin` / `path`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in zrok. Attackers reach the vulnerable code path via ``ProxyShare`` without authentication.
📍 Affected scope
zrok — . Attack surface: `ProxyShare` / `urllib.parse.urljoin` / `urljoin` / `path`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'zrok' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'zrok' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `zrok` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
zrok
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
PyPI
zrok
[{"type":"ECOSYSTEM","events":[{"introduced":"0.4.47"},{"last_affected":"1.1.11"}]}]
References
- advisory https://github.com/advisories/GHSA-jh67-hwqw-m5r7
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45568
- package https://github.com/openziti/zrok
- package https://pypi.org/project/zrok
- patch [email protected]
- web https://github.com/openziti/zrok/security/advisories/GHSA-jh67-hwqw-m5r7
- web [email protected]