Skip to content
Web

CVE-2026-45568

9.9
Critical
EPSS 0.54%Patch availableJul 17, 2026

SSRF in zrok Python SDK ProxyShare allows attacker-controlled server-side requests.

common questions

Is CVE-2026-45568 being exploited?

Not confirmed. CVE-2026-45568 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.54% probability of exploitation in the next 30 days.

How severe is CVE-2026-45568?

CVE-2026-45568 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-45568?

Yes. A fix has been recorded for CVE-2026-45568. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-45568 affect?

CVE-2026-45568 affects zrok Python SDK <2.0.3, ProxyShare Flask proxy route, Deployments using zrok SDK. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-45568?

Upgrade to zrok Python SDK v2.0.3+, validate/block untrusted URLs, restrict outbound requests.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
zrok Python SDK <2.0.3ProxyShare Flask proxy routeDeployments using zrok SDK
impact

Server-Side Request Forgery via absolute URL lets attackers make server-side requests to arbitrary hosts, access internal services, exfiltrate data, and pivot.

action required

Immediate action required

affected versions
openziti zrok
  • affected>= 0.4.47 and < 2.0.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free