CVE-2026-54746: Hatchet allows cross-tenant write/DoS to other tenants' workers via Dispatcher gRPC UpsertWorkerLabels and Unsubscribe
Summary A cross-tenant write / DoS vulnerability in the Hatchet Dispatcher gRPC service allows any holder of a normal tenant-scoped API token (the lowest credential Hatchet issues — an OWNER of a brand-new tenant) to overwrite the affinity labels of, or disconnect from the dispatcher, any worker UUID belonging to any other tenant on the same Hatchet instance.
Published Aug 28, 2026
Affected packages
github.com/hatchet-dev/hatchet
- Ecosystem
- Go
- Affected
- >= 0.40.0, < 0.91.2
- Fixed in
- 0.91.2
- Check
go list -m github.com/hatchet-dev/hatchet
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A cross-tenant write / DoS vulnerability in the Hatchet Dispatcher gRPC service allows any holder of a normal tenant-scoped API token (the lowest credential Hatchet issues — an OWNER of a brand-new tenant) to overwrite the affinity labels of, or disconnect from the dispatcher, any worker UUID belonging to any other tenant on the same Hatchet instance. The two affected RPCs — Dispatcher/UpsertWorkerLabels and Dispatcher/Unsubscribe — read the caller's tenant from the bearer-token context only for analytics and response shaping, and never use it to authorise the worker_id from the request body.
Impact
This CVE requires the attacker to successfully guess the target UUID. Who is impacted. Any Hatchet deployment that hosts more than one tenant on the same instance:
- Hatchet Cloud (multi-tenant SaaS) — every tenant is exposed to every other tenant.
- Self-hosted Hatchet with multiple internal teams / business units sharing one instance — each team is exposed to every other team on the box.
- Any deployment where a single tenant's API token can be obtained by an attacker (e.g. a leaked low-privilege CI token from a single tenant). One token is enough to attack every other tenant on the same instance.
Single-tenant self-hosted deployments are unaffected in practice (the "victim" and "attacker" tenants would be the same).
Credited to sajdakabir.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-61681
Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler
medium4.1Sep 22, 2026CVE-2026-63342
Hatchet: Cross-Tenant Durable Task Event Log Disclosure via Missing Authorization Check
medium6.3Sep 22, 2026CVE-2026-84298
Hatchet: Cross-tenant durable callback payload disclosure in Hatchet V1 Dispatcher
low3.1Sep 22, 2026CVE-2026-88978
Hatchet DurableTask WorkerStatus gRPC resolves caller-supplied durable-task UUIDs via ListSatisfiedEntries with no tenant_id filter
medium4.3Sep 22, 2026CVE-2026-61687
Hatchet - Unauthenticated OAuth state CSRF / login-CSRF via empty-state collision in ValidateOAuthState
high7.1Sep 21, 2026CVE-2026-42572
Hatchet affected by cross-tenant information disclosure in `listTasksByDAGIds`
medium5.3May 6, 2026
