ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-61687

Hatchet - Unauthenticated OAuth state CSRF / login-CSRF via empty-state collision in ValidateOAuthState

Published Sep 21, 2026 · catalog updated Nov 4, 2026 · Hatchet - Unauthenticated OAuth

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-61687. EPSS is 0.17%. Act only if a listed version of Hatchet - Unauthenticated OAuth is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Hatchet - Unauthenticated OAuth).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.17%
Remediation
Version ranges on file
Affected products
Go github.com/hatchet-dev/hatchet · go github.com/hatchet-dev/hatchet

### Summary Hatchet version v0.86.26 and below is vulnerable to OAuth state CSRF (login CSRF / account fixation). The vulnerable code clears the session 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 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 , , 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 HEAD and in every tagged release up to and including v0.86.26 (commit ).

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/hatchet-dev/hatchet0 → 0.91.1
  • go github.com/hatchet-dev/hatchet<0.91.1

How to fix CVE-2026-61687

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-61687. EPSS is 0.17%. Act only if a listed version of Hatchet - Unauthenticated OAuth is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.91.1, <0.91.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-1275; CWE-287: Improper Authentication; CWE-352: Cross-Site Request Forgery (CSRF). EPSS 0.17%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 21, 2026 · GitHub Advisory Database

    Detected

    ### Summary Hatchet version v0.86.26 and below is vulnerable to OAuth state CSRF (login CSRF / account fixation). The vulnerable code clears the session 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 parameter on any later callback request — allowing an unauthenticated attacker to bind an alrea

  2. Nov 4, 2026 · GitHub Advisory Database

    Fix available

    github.com/hatchet-dev/hatchet fixed in 0.91.1

  3. Nov 4, 2026 · GitHub Advisory Database

    Fix available

    github.com/hatchet-dev/hatchet fixed in 0.91.1

  4. Nov 4, 2026 · GitHub Advisory Database

    Updated

    ### Summary Hatchet version v0.86.26 and below is vulnerable to OAuth state CSRF (login CSRF / account fixation). The vulnerable code clears the session 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 parameter on any later callback request — allowing an unauthenticated attacker to bind an alrea

Sources

  • CVE.orgVulnerability recordCVE-2026-61687

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-phg3-3g28-wq9v

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • GitLab Advisory DatabasePackage advisorygo/github.com/hatchet-dev/hatchet/CVE-2026-61687.yml

    Hatchet version v0.86.26 and below is vulnerable to OAuth state CSRF + (login CSRF / account fixation).\n\nThe vulnerable code clears the session + 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 + parameter on any later callback request — allowing an unauthenticated attacker to + bind an alre

    gitlab.com
  • Go Vulnerability DatabasePackage advisoryGHSA-phg3-3g28-wq9v

    Hatchet - Unauthenticated OAuth state CSRF / login-CSRF via empty-state collision in ValidateOAuthState

    osv.dev
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-phg3-3g28-wq9v

    Hatchet - Unauthenticated OAuth state CSRF / login-CSRF via empty-state collision in ValidateOAuthState

    osv.dev

References

Freshness

Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 5, 2026
  • Go Vulnerability DatabaseNov 5, 2026
  • GitLab Advisory DatabaseNov 5, 2026
  • GitHub Advisory DatabaseNov 5, 2026
  • OpenSSF OSV / OSV ScannerNov 5, 2026