What happened
Published 2026-09-21 across four GitHub advisories. Each is a missing-or-consistent tenant/ownership check in Helabet's durable-event and ingestors paths; the UUIDv4 requirement lowers practical exploitability but the pattern is systemic.
Why it matters
Hatchet is explicitly an AI-agent and durable-workflow orchestrator; tenant-boundary failures expose workflow event logs (task names, user messages, branching/wait conditions) and can enable cross-tenant manipulation in multi-tenant agent deployments.
Attack vector
Cluster of multi-tenant authz gaps in the agent orchestrator: durable-task event-log reads without tenant filter (CVE-2026-63342 GET /durable-tasks/{id}), WorkerStatus gRPC polling without tenant filter (CVE-2026-88978), task_external_id routing before tenant ownership check (CVE-2026-84298), and an SNS UnsubscribeConfirmation handler calling http.Get() on an unverified URL (CVE-2026-61681).
Affected systems
Hatchet < 0.106.1 (CVE-2026-88978, CVE-2026-84298, CVE-2026-63342, CVE-2026-61681)
Mitigation
Upgrade to Hatchet 0.91.1 / 0.95.3 / 0.106.1 per advisory (commits 06c1fe435, 15bc7923d, 9555bfdd1, 2d211bce); require the target tenant as a parent resource.