Live › vulnerability › CVE-2026-61687
Go to dashboardHatchet's ValidateOAuthState clears the oauth_state_ session value to an empty string after a successful OAuth callback, then accepts an empty state parameter as a match. An unauthenticated attacker can bind a victim's Hatchet session to an attacker-controlled OAuth identity.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| github.com/hatchet-dev/hatchet | go | < 0.91.2 | 0.91.2 |
0.91.2 (go.mod: github.com/hatchet-dev/hatchet)Upgrade github.com/hatchet-dev/hatchet to 0.91.2 (the sources conflict: the description says 0.91.1).
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Hatchet is a platform for orchestrating background tasks, AI agents, and durable workflows at scale. Prior to 0.91.1, ValidateOAuthState clears the oauth_state_ session value to an empty string after a successful OAuth callback and later accepts an empty state parameter as equal, allowing an unauthenticated attacker to bind a victim's Hatchet session to an attacker-controlled OAuth identity. Exploitation requires the victim to have completed an OAuth flow in the current session and the deployment to enable auth.google.enabled, auth.github.enabled, or the Slack integration. This issue is fixed in version 0.91.1.
This page as .md · .json · in your agent: get_signal("CVE-2026-61687")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.