CVE-2026-84298
Received Received - Intake

Durable Task UUID Exposure in Hatchet

Publication date: 2026-09-21

Last updated on: 2026-09-21

Assigner: GitHub, Inc.

Description
Hatchet is a platform for orchestrating background tasks, AI agents, and durable workflows at scale. Prior to 0.95.3, the V1 DurableTask stream handler stores worker-supplied task_external_id values in the durableInvocations routing map before tenant ownership is verified, and callback delivery resolves that map by task UUID without tenant identity. An authenticated tenant worker that knows another tenant's durable task UUID and keeps a stream open on the same dispatcher process can receive that task's durable callback result payload. UUIDv4 values are not enumerable, and single-tenant deployments are unaffected in practice. This issue is fixed in version 0.95.3.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-21
Last Modified
2026-09-21
Generated
2026-09-21
AI Q&A
2026-09-21
EPSS Evaluated
N/A
NVD
CVE-2026-84298
EUVD
EUVD-2026-83979

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
hatchet hatchet to 0.95.3 (inc)
hatchet-dev hatchet 0.95.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a cross-tenant data disclosure issue in the Hatchet platform's V1 DurableTask stream handler. It occurs because task_external_id values from workers are stored in a routing map before tenant ownership is verified. If a tenant worker knows another tenant's durable task UUID and keeps a stream open, they can receive that tenant's callback result payload even though the task belongs to a different tenant. The issue is fixed in version 0.95.3.

Detection Guidance

Detection requires checking if your Hatchet deployment is running a vulnerable version (prior to 0.95.3) and monitoring for unusual cross-tenant callback deliveries. Review dispatcher logs for errors related to tenant ownership verification failures in the V1 DurableTask stream handler. Check if any tenant workers are maintaining open streams while receiving callbacks not intended for their tenant.

Impact Analysis

An attacker with access to the system could potentially intercept callback results intended for another tenant if they know the target task's UUID. This could lead to unauthorized access to sensitive data. However, exploitation is difficult because UUIDv4 values are not easily guessable and require prior knowledge of the target UUID. Single-tenant deployments are not affected.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or sensitive data, which may violate compliance requirements under GDPR, HIPAA, or other regulations. It undermines data isolation between tenants, potentially resulting in data breaches and non-compliance with privacy and security standards.

Mitigation Strategies

Upgrade to Hatchet version 0.95.3 or later to apply the fix that properly scopes task invocations by tenant ID. For multi-tenant deployments, ensure tenant isolation is enforced at all levels. Review and restrict access to durable task UUIDs to prevent unauthorized knowledge of target UUIDs.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-84298. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart