Vulnerability · CVE-2026-61681
Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler
Published Sep 22, 2026 · catalog updated Nov 4, 2026 · Hatchet: SSRF via Unsigned
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-61681. EPSS is 0.31%. Act only if a listed version of Hatchet: SSRF via Unsigned 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: SSRF via Unsigned).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium4.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.31%
- Remediation
- Version ranges on file
- Affected products
- Go github.com/hatchet-dev/hatchet · go github.com/hatchet-dev/hatchet
### Summary The SNS handler in makes an unvalidated call to without any URL restriction. Because is intentionally excluded from the signed field list, an attacker can replace this field in a legitimately AWS-signed message with an arbitrary internal URL, bypassing the signature check entirely and triggering a Server-Side Request Forgery (SSRF) against internal infrastructure — including the EC2 Instance Metadata Service (IMDS) at . ### Impact This is a Server-Side Request Forgery (SSRF) vulnerability. An attacker with a Hatchet account and an AWS Free Tier account can: - Reach the EC2 IMDS endpoint and retrieve IAM temporary credentials if Hatchet is deployed on AWS - Port-scan and probe internal services not exposed to the internet - Access internal HTTP APIs (e.g., Kubernetes API server, internal dashboards) from the Hatchet server's network context
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-61681
Upgrade
CVE-2026-61681 lists a fix boundary at 0.91.1. Compare the installed build with that boundary before you change production.
Version check
Affected <0.91.1
Advisory
Open the cve_org record and follow its fix.
Official advisories
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-61681. EPSS is 0.31%. Act only if a listed version of Hatchet: SSRF via Unsigned 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-918: Server-Side Request Forgery (SSRF). EPSS 0.31%. 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.
Sep 22, 2026 · GitHub Advisory Database
Detected
### Summary The SNS handler in makes an unvalidated call to without any URL restriction. Because is intentionally excluded from the signed field list, an attacker can replace this field in a legitimately AWS-signed message with an arbitrary internal URL, bypassing the signature check entirely and triggering a Server-Side Request Forgery (SSRF) against internal infrastructure — including the EC2 In
Nov 4, 2026 · GitHub Advisory Database
Fix available
github.com/hatchet-dev/hatchet fixed in 0.91.1
Nov 4, 2026 · GitHub Advisory Database
Fix available
github.com/hatchet-dev/hatchet fixed in 0.91.1
Nov 4, 2026 · GitHub Advisory Database
Updated
### Summary The SNS handler in makes an unvalidated call to without any URL restriction. Because is intentionally excluded from the signed field list, an attacker can replace this field in a legitimately AWS-signed message with an arbitrary internal URL, bypassing the signature check entirely and triggering a Server-Side Request Forgery (SSRF) against internal infrastructure — including the EC2 In
Sources
- CVE.orgVulnerability recordCVE-2026-61681
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-fjwv-jf2v-j499
GitHub Advisory Database record mirrored by OSV.
github.com - GitLab Advisory DatabasePackage advisorygo/github.com/hatchet-dev/hatchet/CVE-2026-61681.yml
The SNS handler in + makes an unvalidated\n call to without any + URL restriction. Because is intentionally\nexcluded from the + signed field list, an attacker can replace this field in a legitimately\nAWS-signed + message with an arbitrary internal URL, bypassing the signature + check entirely and\ntriggering a Server-Side Request
gitlab.com - Go Vulnerability DatabasePackage advisoryGHSA-fjwv-jf2v-j499
Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler
osv.dev - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-fjwv-jf2v-j499
Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler
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