Vulnerability in github.com/hatchet-dev/hatchet (CVE-2026-42572)
Summary
Vulnerability in github.com/hatchet-dev/hatchet (CVE-2026-42572). Confidential information can be exposed externally. Exploitable via GET /api/v1/stable/dags/tasks. Mitigation: upgrade to 0.83.39 or later.
Original description
The description as published by the source.
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.
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-42572 has been found in github.com/hatchet-dev/hatchet.
Attackers can target a specific entry point like GET /api/v1/stable/dags/tasks over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: upgrade github.com/hatchet-dev/hatchet to 0.83.39 or later.
If unsure, ask your IT team or search "github.com/hatchet-dev/hatchet CVE-2026-42572" on the vendor's site.
CVE-2026-42572 (github.com/hatchet-dev/hatchet) — CWE-639 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/stable/dags/tasks / external_id / display_name / action_id
Patched: 0.83.39 — 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 GET /api/v1/stable/dags/tasks.
Check the vendor advisory for the affected versions of github.com/hatchet-dev/hatchet. Attack surface: GET /api/v1/stable/dags/tasks / external_id / display_name / action_id.
Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally.
Update to 0.83.39.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/stable/dags/tasks requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/stable/dags/tasks' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/stable/dags/tasksへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/hatchet-dev/hatchet to 0.83.39ステージング環境で 0.83.39 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/stable/dags/tasks on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com