CVE-2026-32096
SSRF in SNS webhook before 0.7.0 allows unauthenticated outbound GETs.
Is CVE-2026-32096 being exploited?
Not confirmed. CVE-2026-32096 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-32096?
CVE-2026-32096 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-32096?
Yes. A fix has been recorded for CVE-2026-32096. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32096 affect?
CVE-2026-32096 affects Plunk (<0.7.0) open-source email platform on AWS SES. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32096?
Upgrade to 0.7.0+ immediately; review webhook access and outbound controls.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SSRF enables outbound requests to arbitrary hosts; risk of internal access or remote code execution.
Immediate action required
- affected< 0.7.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.