SSRF in Useplunk Plunk
CVE-2026-32096
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.
Vulnerability class: SSRF (Server-Side Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.3 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N.
EPSS exploit prediction
EPSS: 0.004 (34.7th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 35th percentile — 34.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.004 · change: +0.002
Affected products
- Useplunk Plunk — versions < 0.7.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
Frequently asked questions
- What is CVE-2026-32096?
- CVE-2026-32096 is a critical-severity vulnerability in Useplunk Plunk, classified under Server-Side Request Forgery (SSRF). CVSS score: 9.3/10. Published 2026-03-11.
- How severe is CVE-2026-32096?
- Critical severity. CVSS v3 base score is 9.3 out of 10.
- Is CVE-2026-32096 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.