<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 15:42:30 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-61681</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-61681</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-61681</guid>
    </item>
    <item>
      <title>GHSA-fjwv-jf2v-j499 — Hatchet: SSRF via Unsigned UnsubscribeURL in SNS UnsubscribeConfirmation Handler</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-fjwv-jf2v-j499</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: hatchet-dev/hatchet&lt;/p&gt;
&lt;p&gt;### Summary
  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`.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This is a Server-Side Request Forgery (SSRF) vulnerability. An attacker with a Hatchet account and an AWS Free Tier
  account can:&lt;/p&gt;
&lt;p&gt;- 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&amp;#39;s network
  context&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: hatchet-dev/hatchet&lt;/p&gt;
&lt;p&gt;### Summary
  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`.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This is a Server-Side Request Forgery (SSRF) vulnerability. An attacker with a Hatchet account and an AWS Free Tier
  account can:&lt;/p&gt;
&lt;p&gt;- 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&amp;#39;s network
  context&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-fjwv-jf2v-j499</guid>
    </item>
  </channel>
</rss>
