Advisory

GHSA-cpf9-ph2j-ccr9

Also known as: CVE-2026-40303, GO-2026-5329

Summary

zrok: Unauthenticated DoS via unbounded memory allocation in striped session cookie parsing

Details

Summary
endpoints.GetSessionCookie parses an attacker-supplied cookie chunk count and calls make([]string, count) with no upper bound before any token validation occurs. The function is reached on every request to an OAuth-protected proxy share, allowing an unauthenticated remote attacker to trigger gigabyte-scale heap allocations per request, leading to process-level OOM termination or repeated goroutine panics. Both publicProxy and dynamicProxy are affected.

  • Attack Vector: Network — exploitable via a single HTTP request with a crafted Cookie header.
  • Attack Complexity: Low — no preconditions or chaining required; the attacker only needs to know the cookie name (publicly derivable from any OAuth redirect).
  • Privileges Required: None — reached before JWT validation or any authentication check.
  • User Interaction: None.
  • Scope: Unchanged — impact is confined to the affected proxy process.
  • Confidentiality Impact: None.
  • Integrity Impact: None.

Availability Impact: High — sustained or concurrent requests cause OOM process termination, taking down the proxy for all users of all shares it serves.

Affected Components

  • endpoints/oauthCookies.go — GetSessionCookie (line 81)
  • endpoints/publicProxy/authOAuth.go — handleOAuth (line 50) — call site, pre-auth
  • endpoints/dynamicProxy/cookies.go — getSessionCookie (line 29) — call site

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-04-16 21:09 UTC
Modified
2026-06-25 19:56 UTC

Affected packages and fixes

github.com/openziti/zrok

Go · All systems

Affected

  • introduced 0, last affected 1.1.11 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/openziti/zrok/v2

Go · All systems

Affected

  • introduced 0, fixed 2.0.1 (semver)

Fixed versions

2.0.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences