# CVE-2026-84298: Hatchet: Cross-tenant durable callback payload disclosure in Hatchet V1 Dispatcher

> An authenticated worker can read another tenant's durable callback payload by knowing the task UUID, exposing sensitive workflow data.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/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:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-9q4h-f4x5-ffq8, GO-2026-6561

## What is CVE-2026-84298?

CVE-2026-84298 is a low-severity missing authorization vulnerability in hatchet-dev hatchet, published on 21 Sep 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.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.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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


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

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

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

## Is CVE-2026-84298 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84298 is a low-severity missing authorization vulnerability in hatchet-dev hatchet, published on 21 Sep 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-84298 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.95.3
- github.com/hatchet-dev/hatchet (Go): affected all versions; fixed in 0.95.3
- github.com/hatchet-dev/hatchet (Go): affected all versions; fixed in 0.95.3

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-84298/ (Markdown: https://insights.sbomify.com/CVE-2026-84298/index.md)
```

## Sources

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

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