CVE-2026-45568

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 19, 2026

Last Modified

July 20, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

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 / EcosystemFix (by version range) / PatchReleasedSource
pipzrok—ghsa

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 rangeFix by version rangeDependents
zrok0.4.47 ... 1.1.9 (22 versions)
  • 0.4.47 through 1.1.11: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 203 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-20 11:34 UTCEG score recompute
  2. 2026-10-20 11:33 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  3. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-19 11:33 UTCEG score recompute
  5. 2026-10-19 11:33 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  6. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-18 09:17 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  8. 2026-10-18 03:38 UTCEG score recompute
  9. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-17 07:35 UTCEG score recompute
  11. 2026-10-17 07:34 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  12. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-16 07:34 UTCEG score recompute
  14. 2026-10-16 07:34 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  15. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-15 06:29 UTCEG score recompute
  17. 2026-10-15 06:28 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-14 02:08 UTCEG score recompute
  20. 2026-10-14 02:08 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-12 22:30 UTCEG score recompute
  23. 2026-10-12 22:29 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  24. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-12 16:04 UTCEG score recompute
Show 75 more
  1. 2026-10-12 07:44 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  2. 2026-10-11 19:46 UTCEG score recompute
  3. 2026-10-11 17:00 UTCEG score recompute
  4. 2026-10-11 14:26 UTCEG score recompute
  5. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-09-30 11:17 UTCOSV refresh
  17. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  26. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  27. 2026-09-11 18:10 UTCOSV refresh
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  29. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  30. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  33. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  34. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  35. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  37. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  40. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  41. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  43. 2026-08-23 21:31 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  44. 2026-08-23 17:05 UTCEG score recompute
  45. 2026-08-23 17:05 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  46. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  48. 2026-08-21 23:38 UTCEG score recompute
  49. 2026-08-21 23:38 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  50. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-08-20 19:02 UTCEG score recompute
  52. 2026-08-20 19:02 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  53. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  54. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  55. 2026-08-17 14:40 UTCEG score recompute
  56. 2026-08-17 14:40 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  57. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  58. 2026-08-17 10:00 UTCEG score recompute
  59. 2026-08-17 10:00 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  60. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  61. 2026-08-16 12:18 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  62. 2026-08-16 07:57 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  63. 2026-08-16 03:35 UTCEG score recompute
  64. 2026-08-16 03:35 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  65. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  66. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  67. 2026-08-14 23:52 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  68. 2026-08-14 19:31 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  69. 2026-08-14 15:10 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  70. 2026-08-14 10:49 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  71. 2026-08-14 06:28 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  72. 2026-08-14 02:07 UTCEG score recompute
  73. 2026-08-14 02:07 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL
  74. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  75. 2026-08-13 10:45 UTCGHSA enrichmentGHSA-jh67-hwqw-m5r7 · GitHub severity CRITICAL

Frequently asked(5)

What is CVE-2026-45568?
CVE-2026-45568 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-45568 published?
The CVE record for CVE-2026-45568 was published on May 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 20, 2026; the record at its source may have been updated since.
Is CVE-2026-45568 actively exploited?
CVE-2026-45568 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-45568 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45568 are linked in the Vendor Advisories panel on this page.

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.