CVE-2026-54746 Hatchet: Cross-tenant write/DoS to other tenants' workers via Dispatcher gRPC UpsertWorkerLabels and Unsubscribe
Authenticated users can modify or disconnect other tenants' workers by guessing UUIDs, causing cross-tenant integrity issues and denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54746?
CVE-2026-54746 is a medium-severity missing authorization vulnerability in hatchet-dev hatchet, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Hatchet is a platform for orchestrating background tasks, AI agents, and durable workflows at scale. From 0.40.0 until 0.91.1, the Dispatcher gRPC service does not verify that a request's worker ID belongs to the tenant identified by the bearer-token context in Dispatcher/UpsertWorkerLabels and Dispatcher/Unsubscribe. An authenticated owner of any tenant who guesses another tenant's worker UUID can overwrite that worker's affinity labels or disconnect the worker from the dispatcher. This can cause cross-tenant integrity impact and denial of service on multi-tenant Hatchet Cloud or shared self-hosted deployments. Single-tenant deployments are not practically affected because the attacker and target tenant are the same. This issue is fixed in version 0.91.1.
Which versions are affected by CVE-2026-54746?
3 open source packages ship an affected version, including github.com/hatchet-dev/hatchet.
| Package | Affected | Fixed in |
|---|---|---|
github.com/hatchet-dev/hatchet Go | From 0.40.0 | 0.91.2 |
github.com/hatchet-dev/hatchet Go | From 0.40.0 | 0.91.2 |
github.com/hatchet-dev/hatchet Go | From 0.40.0 | 0.91.2 |
How do I fix CVE-2026-54746?
Upgrade github.com/hatchet-dev/hatchet to 0.91.2 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-54746 being exploited?
There is no known exploitation of CVE-2026-54746 in the wild and no public exploit code.
Sources
Also known as GHSA-8x7x-83cf-c3pg, GO-2026-6309.