CVE-2026-61681

MEDIUMPre-NVD 4.14.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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
4.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.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, the SNS UnsubscribeConfirmation handler in internal/integrations/ingestors/sns/sns.go calls http.Get() on payload.UnsubscribeURL after VerifyPayload() even though BuildSignature() excludes UnsubscribeURL, allowing an authenticated Hatchet tenant to replace that field in an otherwise valid AWS-signed message with an internal URL. The server-side request can reach EC2 Instance Metadata Service, internal services, and internal HTTP APIs, potentially exposing IAM credentials or network-accessible data and functionality. This issue is fixed in version 0.91.1.

CVSS v3
4.1
EG Score
4.1(medium)
EG Risk
19(Track)
EG Risk 19/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
Severity41% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
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 2d211bce16e5 (hatchet-dev/hatchet)

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

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

SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler · Advisory · hatchet-dev/hatchet · GitHub

https://github.com/hatchet-dev/hatchet/security/advisories/GHSA-fjwv-jf2v-j499

Vendor Advisories for CVE-2026-61681(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-dev/hatchet—0.91.1—

Weakness Classification(1)

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 23:38 UTCEG score recompute
  2. 2026-09-24 22:27 UTCEG score recompute
  3. 2026-09-24 19:38 UTCEG score recompute
  4. 2026-09-23 18:39 UTCEG score recompute
  5. 2026-09-23 17:54 UTCEPSS rescore
  6. 2026-09-22 17:40 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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61681?
CVE-2026-61681 is a medium 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, the SNS UnsubscribeConfirmation handler in internal/integrations/ingestors/sns/sns.go calls http.Get() on payload.UnsubscribeURL after VerifyPayload() even though BuildSignature()…
When was CVE-2026-61681 disclosed?
CVE-2026-61681 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-61681 actively exploited?
CVE-2026-61681 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 78.7% of all scored CVEs.
What is the CVSS score of CVE-2026-61681?
CVE-2026-61681 has a CVSS v3 base score of 4.1 (NVD).
How do I remediate CVE-2026-61681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61681, 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-61681

Explore →

Is Your Infrastructure Affected by CVE-2026-61681?

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

Book a Demo →Browse All CVEs