Authentication Bypass in hatchet (CVE-2026-61687)
Summary
Authentication bypass in hatchet (CVE-2026-61687). Data can be tampered with by attackers. Exploitable via auth.google.enabled. Mitigation: upgrade to 0.91.1 or later.
Original description
The description as published by the source.
Summary
Hatchet version v0.86.26 and below is vulnerable to OAuth state CSRF (login CSRF / account fixation).
The vulnerable code clears the session oauth_state_ value to the empty string "" after a successful OAuth callback rather than removing the key, and the subsequent state-equality check then accepts an empty ?state= parameter on any later callback request — allowing an unauthenticated attacker to bind an already-authenticated victim's session cookie to an attacker-controlled OAuth identity (account takeover via login-CSRF).
Impact
Affected configurations: any deployment that has enabled at least one of auth.google.enabled, auth.github.enabled, or the Slack integration, and where the victim has completed at least one OAuth flow on that integration in the current session. Bug present on main HEAD and in every tagged release up to and including v0.86.26 (commit 243f41d9e1161e70d47dfc0a6509f1c4ddfc9c23).
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-61687 has been found in hatchet.
Attackers can target a specific entry point like auth.google.enabled over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade hatchet to 0.91.1 or later.
If unsure, ask your IT team or search "hatchet CVE-2026-61687" on the vendor's site.
CVE-2026-61687 (hatchet) — CWE-287 / CVSS v3 7.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: auth.google.enabled / auth.github.enabled / main
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.
Authentication bypass (CWE-287) exists in hatchet. Attackers reach the vulnerable code path via auth.google.enabled without authentication.
Check the vendor advisory for the affected versions of hatchet. Attack surface: auth.google.enabled / auth.github.enabled / main.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
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' . 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
hatchetを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade 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 github.com