CVE-2026-45568

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
28.6%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 20, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

zrok Python ProxyShare can be used as an SSRF proxy through absolute URL paths · Advisory · openziti/zrok · GitHub

https://github.com/openziti/zrok/security/advisories/GHSA-jh67-hwqw-m5r7
github_release Patch Available

v2.0.3

Patch available: openziti/zrok v2.0.3

https://github.com/openziti/zrok/releases/tag/v2.0.3
github_commit

commit 7c1dc3ecd1c8 (openziti/zrok)

Fix landed in openziti/zrok commit 7c1dc3ecd1c8 — awaiting tagged release

https://github.com/openziti/zrok/commit/7c1dc3ecd1c89d8cd2e845a72c3878bd2d31b4fe

Vendor Advisories for CVE-2026-45568(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipzrokghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
zrok0.4.47 ... 1.1.9 (22 versions)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:16 UTCEG score recompute 0.80
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-20 03:15 UTCNVD updateCVSS v3 → 9.1
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 16:54 UTCEG score recompute 9.90
  11. 2026-07-16 16:54 UTCGHSA enrichment
  12. 2026-07-16 16:53 UTCMITRE cvelistV5CVSS v3 → 9.9 · CVSS v4 → 9.9
  13. 2026-06-29 20:55 UTCGHSA enrichment
  14. 2026-06-25 17:07 UTCGHSA enrichment
  15. 2026-06-17 01:28 UTCGHSA enrichment
  16. 2026-06-14 23:18 UTCEPSS rescore
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-13 22:42 UTCGHSA enrichment
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-10 13:22 UTCGHSA enrichment
  21. 2026-06-07 10:35 UTCGHSA enrichment
  22. 2026-06-04 07:49 UTCGHSA enrichment
  23. 2026-06-01 05:02 UTCGHSA enrichment
  24. 2026-05-24 06:14 UTCEG score recompute
  25. 2026-05-24 06:14 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-45568?
CVE-2026-45568 is a critical vulnerability published on May 19, 2026. 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…
When was CVE-2026-45568 disclosed?
CVE-2026-45568 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45568 actively exploited?
CVE-2026-45568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45568?
CVE-2026-45568 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-45568?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45568, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45568

Explore →

Is Your Infrastructure Affected by CVE-2026-45568?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.