Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.4amended

Hatchet allows cross-tenant write/DoS to other tenants' workers via Dispatcher gRPC UpsertWorkerLabels and Unsubscribe

CVE-2026-54746GHSA-8x7x-83cf-c3pg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/hatchet-dev/hatchet 0.91.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L
EPSS
  • CVE-2026-54746: 0.37% estimated exploitation activity in the next 30 days; percentile 30.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 workerid 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-8x7x-83cf-c3pg

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6309

  3. Revision 1 · created ·

    Published from osv record GHSA-8x7x-83cf-c3pg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54746

Advisory: Hatchet allows cross-tenant write/DoS to other tenants' workers via Dispatcher gRPC UpsertWorkerLabels and Unsubscribe
IDs: CVE-2026-54746, GHSA-8x7x-83cf-c3pg
Record: https://patchnext.com/advisories/cve-2026-54746 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/hatchet-dev/hatchet 0.91.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/hatchet-dev/hatchet: affected >= 0.40.0, < 0.91.2; fixed in 0.91.2

## Suggested inspection (read-only)
- Go github.com/hatchet-dev/hatchet: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/hatchet-dev/hatchet.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8x7x-83cf-c3pg (OSV record GHSA-8x7x-83cf-c3pg lists affected ranges: Go github.com/hatchet-dev/hatchet >=0.40.0 <0.91.2 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6309 (OSV record GO-2026-6309 lists affected ranges: Go github.com/hatchet-dev/hatchet >=0.40.0 <0.91.2 (fixed))
- Verified: https://github.com/advisories/GHSA-8x7x-83cf-c3pg (GitHub-reviewed advisory GHSA-8x7x-83cf-c3pg lists affected ranges: Go github.com/hatchet-dev/hatchet >=0.40.0 <0.91.2)

Commands are suggestions: review each one before running it.

Loading voting…