CVE-2026-61687 hatchet - Unauthenticated OAuth state CSRF / login-CSRF via empty-state collision in ValidateOAuthState
An attacker can bind a victim's session to an attacker-controlled OAuth identity via empty-state collision, requiring specific auth integrations to be enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-61687?
CVE-2026-61687 is a high-severity vulnerability in hatchet-dev hatchet, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Which versions are affected by CVE-2026-61687?
3 open source packages ship an affected version, including github.com/hatchet-dev/hatchet and hatchet.
| Package | Affected | Fixed in |
|---|---|---|
github.com/hatchet-dev/hatchet Go | All versions | 0.91.2 |
hatchet Go | All versions | 0.91.1 |
hatchet Go | All versions | 0.91.1 |
How do I fix CVE-2026-61687?
Upgrade github.com/hatchet-dev/hatchet to 0.91.2 or later.
Is CVE-2026-61687 being exploited?
There is no known exploitation of CVE-2026-61687 in the wild and no public exploit code.
Sources
Also known as GHSA-phg3-3g28-wq9v, GO-2026-6535.