High (7.1) in hatchet-dev hatchet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/hatchet-dev/hatchet 0.91.1, 0.91.2.
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.
Severity
CVSS 3.1
7.1 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
EPSS
0.2%(unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-287Improper Authentication CWE-352Cross-Site Request Forgery (Cross Site Reference Forgery) CWE-384Session Fixation CWE-1275Sensitive Cookie with Improper SameSite Attribute
Show the promptExplain CVE-2026-61687 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61687?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61687?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61687 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.
Attack patterns (CAPEC)
CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
CAPEC-462 Cross-Domain Search Timing Severity: Medium