Vulnerability in github.com/hatchet-dev/hatchet (CVE-2026-88978)
Summary
Vulnerability in github.com/hatchet-dev/hatchet (CVE-2026-88978). Risk of unauthorized operations or information disclosure. Exploitable via DurableTask. Mitigation: upgrade to 0.106.1 or later.
Original description
The description as published by the source.
Cross-tenant disclosure risk on DurableTask bidi RPC
This is a low-severity, low-risk cross-tenant data exposure vuln caused by blindly accepting a durable task id, in addition to a list of node and branch ids that identify records in that task's event log, and returning them to the caller via the handleWorkerStatus polling path.
Impact
This advisory requires an attacker to successfully guess a durable task's external uuid belonging to another tenant. External ids are generated uuid v4s (uuid.New() in Go), so exploitation requires prior knowledge of a target task UUID through an out-of-band channel. Thus, while the following environments are impacted, there is an extremely low probability it would be exploited.
Who is impacted. Any Hatchet deployment that hosts more than one tenant on the same instance:
- Hatchet Cloud (multi-tenant SaaS)
- Self-hosted Hatchet with multiple internal teams / business units sharing one instance
- Any deployment where a single tenant's API token can be obtained by an attacker
Single-tenant self-hosted deployments are unaffected in practice (the "victim" and "attacker" tenants would be the same).
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-88978 has been found in github.com/hatchet-dev/hatchet.
Attackers can target a specific entry point like DurableTask over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/hatchet-dev/hatchet to 0.106.1 or later.
If unsure, ask your IT team or search "github.com/hatchet-dev/hatchet CVE-2026-88978" on the vendor's site.
CVE-2026-88978 (github.com/hatchet-dev/hatchet) — CWE-639 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DurableTask / handleWorkerStatus
Patched: 0.106.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in github.com/hatchet-dev/hatchet. Attackers reach the vulnerable code path via DurableTask.
Check the vendor advisory for the affected versions of github.com/hatchet-dev/hatchet. Attack surface: DurableTask / handleWorkerStatus.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 0.106.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/hatchet-dev/hatchet' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/hatchet-dev/hatchet' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/hatchet-dev/hatchetを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/hatchet-dev/hatchet to 0.106.1ステージング環境で 0.106.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com