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.
CVE-2026-32096
HIGHNVD 8.68.6
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: nvd
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(low)
- EG Risk
- 43(Track)EG Risk 43/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity86% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
March 11, 2026
Last Modified
June 17, 2026
References (2)
- security-advisories@githubhttps://github.com/useplunk/plunk/commit/b8f1ad9ab53c78f8ef063fdc125f397c8bfc7652
- security-advisories@githubhttps://github.com/useplunk/plunk/security/advisories/GHSA-xpqg-p8mp-7g44
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:41 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-32096?
CVE-2026-32096 is a high vulnerability published on March 11, 2026. 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…
When was CVE-2026-32096 disclosed?
CVE-2026-32096 was first published in the National Vulnerability Database on March 11, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32096 actively exploited?
CVE-2026-32096 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.5% of all scored CVEs.
What is the CVSS score of CVE-2026-32096?
CVE-2026-32096 has a CVSS v3 base score of 8.6 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-32096?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32096, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32096
Is Your Infrastructure Affected by CVE-2026-32096?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.