Hatchet affected by cross-tenant information disclosure in listTasksByDAGIds

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-42572: 0.18% estimated exploitation activity in the next 30 days; percentile 7.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A missing authorization directive on the GET /api/v1/stable/dags/tasks endpoint caused Hatchet's tenant-membership check to be skipped for this route. A user authenticated to any tenant on the same Hatchet instance could query the endpoint with another tenant's UUID and a DAG UUID belonging to that tenant, and receive task metadata for that DAG. This issue has been patched in v0.83.39. Hatchet Cloud has been patched and requires no action from users. Self-hosted users should upgrade. Impact Who is affected. Multi-tenant Hatchet instances reachable by an attacker who can obtain an account on that instance. On Hatchet Cloud, account creation is open by default. On self-hosted instances, the API must be reachable by the attacker and the hostname known; instances deployed inside a VPC or with signup restricted are not exposed to arbitrary external actors. Prerequisites for exploitation. An attacker needed: 1. An account on the target Hatchet instance. 2. The victim tenant's UUID.…

Published by the source

6 May 2026, 21:59 UTC

Last modified by the source

14 May 2026, 20:53 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-55gc-6fmc-fpx9

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

# Patch Next advisory brief: CVE-2026-42572

Advisory: Hatchet affected by cross-tenant information disclosure in `listTasksByDAGIds`
IDs: CVE-2026-42572, GHSA-55gc-6fmc-fpx9
Record: https://patchnext.com/advisories/cve-2026-42572 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
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.83.39. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/hatchet-dev/hatchet: affected <= 0.83.38; fixed in 0.83.39

## 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://github.com/advisories/GHSA-55gc-6fmc-fpx9 (GitHub-reviewed advisory GHSA-55gc-6fmc-fpx9 lists affected ranges: Go github.com/hatchet-dev/hatchet >=0 <=0.83.38)

Commands are suggestions: review each one before running it.