SSRF (Server-Side Request Forgery) in hatchet-dev/hatchet (CVE-2026-61681)
Summary
SSRF in hatchet-dev/hatchet (CVE-2026-61681). Risk of unauthorized operations or information disclosure. Exploitable via UnsubscribeConfirmation. Mitigation: upgrade to 0.91.1 or later.
Original description
The description as published by the source.
Summary
The SNS UnsubscribeConfirmation handler in internal/integrations/ingestors/sns/sns.go makes an unvalidated
http.Get() call to payload.UnsubscribeURL without any URL restriction. Because UnsubscribeURL is intentionally
excluded from the BuildSignature() signed field list, an attacker can replace this field in a legitimately
AWS-signed message with an arbitrary internal URL, bypassing the VerifyPayload() signature check entirely and
triggering a Server-Side Request Forgery (SSRF) against internal infrastructure — including the EC2 Instance Metadata
Service (IMDS) at 169.254.169.254.
Impact
This is a Server-Side Request Forgery (SSRF) vulnerability. An attacker with a Hatchet account and an AWS Free Tier
account can:
- Reach the EC2 IMDS endpoint and retrieve IAM temporary credentials if Hatchet is deployed on AWS
- Port-scan and probe internal services not exposed to the internet
- Access internal HTTP APIs (e.g., Kubernetes API server, internal dashboards) from the Hatchet server's network
context
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-61681 has been found in hatchet-dev/hatchet.
Attackers can target a specific entry point like UnsubscribeConfirmation over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.1/10.
What to do: upgrade hatchet-dev/hatchet to 0.91.1 or later.
If unsure, ask your IT team or search "hatchet-dev/hatchet CVE-2026-61681" on the vendor's site.
CVE-2026-61681 (hatchet-dev/hatchet) — CWE-918 / CVSS v3 4.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: UnsubscribeConfirmation / payload.UnsubscribeURL / UnsubscribeURL
Patched: 0.91.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.
SSRF (CWE-918) exists in hatchet-dev/hatchet. Attackers reach the vulnerable code path via UnsubscribeConfirmation.
Check the vendor advisory for the affected versions of hatchet-dev/hatchet. Attack surface: UnsubscribeConfirmation / payload.UnsubscribeURL / UnsubscribeURL.
Severity: Medium (CVSS 4.1/10). Risk of unauthorized operations or information disclosure.
Update to 0.91.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 '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 'hatchet-dev/hatchet' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
hatchet-dev/hatchetを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade hatchet-dev/hatchet to 0.91.1ステージング環境で 0.91.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