PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-61687 hatchet-dev CVE debrief

CVE-2026-61687 debrief: Unauthenticated OAuth state CSRF via empty-state collision in ValidateOAuthState in github.com/hatchet-dev/hatchet. This high-severity vulnerability allows unauthenticated CSRF attacks. Defenders should prioritize verification of the fixed version and assess exposure in their environments. The vulnerability exists in the github.com/hatchet-dev/hatchet package, and a fixed version (0.91.2) has been released. Limited information is available about potential exploitation and impact.

Vendor
hatchet-dev
Product
github.com/hatchet-dev/hatchet
CVSS
HIGH 7.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-28
Original CVE updated
2026-10-07
Advisory published
2026-09-28
Advisory updated
2026-10-07

Who should care

Defenders responsible for maintaining or securing applications using the github.com/hatchet-dev/hatchet package should assess exposure to this vulnerability and prioritize verification of the fixed version.

Why it matters

CVE-2026-61687 is a high-severity vulnerability in the github.com/hatchet-dev/hatchet package that could allow unauthenticated CSRF attacks. Defenders should prioritize verification of the fixed version and assess exposure in their environments.

  • Potential CSRF attacks targeting the ValidateOAuthState function.
  • Need to verify the presence of the fixed version (0.91.2) for the affected package.
  • Possible disruption to authentication mechanisms if exploited.

Technical summary

The github.com/hatchet-dev/hatchet package is vulnerable to an unauthenticated OAuth state CSRF attack via empty-state collision in the ValidateOAuthState function. A fixed version (0.91.2) has been released. Defenders should prioritize verifying the presence of the fixed version and assess exposure in their environments. The vulnerability allows unauthenticated CSRF attacks, and limited information is available about potential exploitation and impact. The source corpus provides limited information about the vulnerability, including its existence in the github.com/hatchet-dev/hatchet package and a fixed version of 0.91.2.

Defensive priority

Defenders should prioritize verifying the presence of the fixed version (0.91.2) for the affected package (github.com/hatchet-dev/hatchet) and assess exposure in their environments.

Recommended defensive actions

  • Verify the presence of the fixed version (0.91.2) for the affected package (github.com/hatchet-dev/hatchet) in your environment.
  • Assess exposure to the vulnerability in your environment.
  • Monitor for potential CSRF attacks targeting the ValidateOAuthState function.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The source corpus provides limited information about the vulnerability, including its existence in the github.com/hatchet-dev/hatchet package and a fixed version of 0.91.2. However, details about potential exploitation, impact, and affected versions are not explicitly stated.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-61687 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-61687

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-61687 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-61687

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.