Summary
Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler
The SNS UnsubscribeConfirmation handler in internal/integrations/ingestors/sns/sns.go makes an unvalidated
http.Get() call to payload.UnsubscribeURL without any URL restriction. Because UnsubscribeURL is intentionally
excluded from the BuildSignature() signed field list, an attacker can replace this field in a legitimately
AWS-signed message with an arbitrary internal URL, bypassing the VerifyPayload() signature check entirely and
triggering a Server-Side Request Forgery (SSRF) against internal infrastructure, including the EC2 Instance Metadata
Service (IMDS) at 169.254.169.254.
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
Impact
Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.
CVE-2026-61681 has a CVSS score of 4.1 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.91.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-61681? CVE-2026-61681 is a medium-severity server-side request forgery (SSRF) vulnerability in hatchet-dev/hatchet (go), affecting versions < 0.91.1. It is fixed in 0.91.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
- How severe is CVE-2026-61681? CVE-2026-61681 has a CVSS score of 4.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of hatchet-dev/hatchet are affected by CVE-2026-61681? hatchet-dev/hatchet (go) versions < 0.91.1 is affected.
- Is there a fix for CVE-2026-61681? Yes. CVE-2026-61681 is fixed in 0.91.1. Upgrade to this version or later.
- Is CVE-2026-61681 exploitable, and should I be worried? Whether CVE-2026-61681 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-61681 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-61681? Upgrade
hatchet-dev/hatchetto 0.91.1 or later.