CVE-2026-61687

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 21, 2026
Patch available. Sources: github, github_commit.
github_commit

commit f90464189ad6 (hatchet-dev/hatchet)

Fix landed in hatchet-dev/hatchet commit f90464189ad6 — awaiting tagged release

https://github.com/hatchet-dev/hatchet/commit/f90464189ad642251e09412d0f99fde353036428
github Patch Available

hatchet <= v0.86.26 - Unauthenticated OAuth state CSRF / login-CSRF via empty-state collision in ValidateOAuthState · Advisory · hatchet-dev/hatchet · GitHub

https://github.com/hatchet-dev/hatchet/security/advisories/GHSA-phg3-3g28-wq9v

Vendor Advisories for CVE-2026-61687(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
hatchet—0.91.1—

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 15:59 UTCEG score recompute
  2. 2026-09-24 04:53 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 19:36 UTCEG score recompute
  5. 2026-09-21 21:23 UTCEG score recompute
  6. 2026-09-21 20:48 UTCEG score recompute
  7. 2026-09-21 16:24 UTCEG score recompute
  8. 2026-09-21 15:50 UTCEG score recompute
  9. 2026-09-21 15:50 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61687?
CVE-2026-61687 is a high vulnerability published on September 21, 2026. Hatchet is a platform for orchestrating background tasks, AI agents, and durable workflows at scale. Prior to 0.91.1, ValidateOAuthState clears the oauthstate session value to an empty string after a successful OAuth callback and later accepts an empty state parameter as equal, allowing an…
When was CVE-2026-61687 disclosed?
CVE-2026-61687 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61687 actively exploited?
CVE-2026-61687 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-61687?
CVE-2026-61687 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-61687?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61687, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61687

Explore →

Is Your Infrastructure Affected by CVE-2026-61687?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.