CVE-2026-54746

Received Received - Intake

Privilege Escalation in Hatchet Dispatcher Service

Publication date: 2026-08-28

Last updated on: 2026-08-28

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-28

Last Modified

2026-08-28

Generated

2026-08-29

AI Q&A

2026-08-29

EPSS Evaluated

N/A

NVD

CVE-2026-54746

EUVD

EUVD-2026-67791

Affected Vendors & Products

Vendor	Product	Version / Range
hatchet	hatchet	to 0.91.1 (inc)
hatchet	hatchet	0.91.1

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

This vulnerability affects the Hatchet platform, which orchestrates background tasks and workflows. It exists in versions 0.40.0 to 0.91.1 where the Dispatcher gRPC service does not verify if a worker ID in a request belongs to the tenant identified by the bearer token. An authenticated tenant owner can guess another tenant's worker UUID and overwrite its affinity labels or disconnect it, causing cross-tenant integrity impact and denial of service.

Detection Guidance

Check for unauthorized modifications to worker labels or unexpected worker disconnections in Hatchet logs. Monitor gRPC traffic for Dispatcher/UpsertWorkerLabels and Dispatcher/Unsubscribe requests with mismatched tenant IDs and worker UUIDs.

Impact Analysis

If you use a multi-tenant Hatchet deployment, an attacker with a tenant-scoped token could disrupt other tenants' workers by modifying labels or disconnecting them. This could lead to service disruptions or data integrity issues. Single-tenant deployments are less affected as the attacker and target are the same.

Compliance Impact

This vulnerability could impact compliance by allowing unauthorized access to or disruption of tenant-specific data and services. For GDPR, it may affect data integrity and availability. For HIPAA, it could compromise the confidentiality and integrity of protected health information if workers handling such data are disrupted.

Mitigation Strategies

Upgrade to Hatchet version 0.91.1 or later to apply the patch. Review and restrict tenant-scoped API token permissions. Monitor for suspicious cross-tenant worker operations in logs.

Hi! I’m here to help you understand CVE-2026-54746. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70