Quick answers
- Is CVE-2026-54746 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54746 being exploited in the wild.
- How severe is CVE-2026-54746?
- Medium severity, with a CVSS score of 6.4, published 28 August 2026.
- Which products and versions are affected?
- github.com/hatchet-dev/hatchet (Go) >= 0.40.0, < 0.91.2, SEMVER:introduced=0.40.0,fixed=0.91.2.
- Is there a fix for CVE-2026-54746?
- Yes. github.com/hatchet-dev/hatchet (Go): upgrade to 0.91.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54746 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-54746?
- Check whether you run github.com/hatchet-dev/hatchet (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/hatchet-dev/hatchet (Go): upgrade to 0.91.2 or later
go get github.com/hatchet-dev/hatchet@v0.91.2
Technical details
The vulnerability is a missing authorization check (CWE-862) in two Dispatcher RPC methods: UpsertWorkerLabels and Unsubscribe. These methods accept a worker_id in the request body but fail to validate that the worker belongs to the caller's tenant, even though they read the caller's tenant from the bearer-token context. An attacker with any valid tenant-scoped API token (e.g., an OWNER token from a newly created tenant or a leaked CI token) can craft gRPC requests targeting worker UUIDs from other tenants. While UUID guessing is required, successful exploitation allows the attacker to overwrite worker affinity labels (causing job misrouting) or forcibly disconnect workers (causing denial of service). The vulnerability affects Hatchet versions 0.40.0 through 0.91.1 and is patched in 0.91.2.
Affected products
- Hatchet Hatchet 0.40.0 to 0.91.1
Identifiers
- CVE-2026-54746
- GHSA-8x7x-83cf-c3pg
- GO-2026-6309
Timeline
- 2026-06-30: disclosed
- 2026-08-28: patched: Fixed in version 0.91.2