# CVE-2026-42572: Hatchet: Cross-tenant information disclosure in `listTasksByDAGIds`

> Authenticated users can access task metadata from other tenants due to missing authorization checks on a specific API endpoint.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-55gc-6fmc-fpx9, GO-2026-5134

## What is CVE-2026-42572?

CVE-2026-42572 is a medium-severity missing authorization vulnerability in hatchet-dev hatchet, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Hatchet is a platform for orchestrating background tasks, AI agents, and durable workflows at scale. Prior to 0.83.39, 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 vulnerability is fixed in 0.83.39.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-42572?

3 open source packages ship an affected version, including github.com/hatchet-dev/hatchet. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hatchet-dev/hatchet` | Go | All versions | 0.83.39 |
| `github.com/hatchet-dev/hatchet` | Go | All versions | 0.83.39 |
| `github.com/hatchet-dev/hatchet` | Go | All versions | 0.83.39 |

Products: Hatchet Hatchet.

## How do I fix CVE-2026-42572?

Upgrade github.com/hatchet-dev/hatchet to 0.83.39 or later.

## Is CVE-2026-42572 being exploited?

There is no known exploitation of CVE-2026-42572 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42572 and fix it if it is affected.

What it is: CVE-2026-42572 is a medium-severity missing authorization vulnerability in hatchet-dev hatchet, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42572 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hatchet-dev/hatchet (Go): affected all versions; fixed in 0.83.39
- github.com/hatchet-dev/hatchet (Go): affected all versions; fixed in 0.83.39
- github.com/hatchet-dev/hatchet (Go): affected all versions; fixed in 0.83.39

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42572/ (Markdown: https://insights.sbomify.com/CVE-2026-42572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42572
- OSV: https://osv.dev/vulnerability/CVE-2026-42572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42572/
Summaries are generated and may contain mistakes; the official description above is the record.