What is the CVSS score of CVE-2026-32096?

CVE-2026-32096 has a CVSS 3.1 base score of 9.3 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2026-32096?

Within 24 hours: Identify all instances running Plunk version 0.7.0 or earlier and isolate them from production networks if possible; disable external access to affected instances and document inventory. Within 7 days: Implement network segmentation to restrict Plunk instances from accessing internal systems, AWS metadata endpoints, and sensitive services; deploy WAF rules to block suspicious request patterns. Within 30 days: Upgrade to Plunk version 0.7.1 or later once available; if upgrade is not feasible, evaluate alternative email solutions or implement comprehensive air-gapping of affected systems.

Plunk CVE-2026-32096

CRITICAL

Server-Side Request Forgery (SSRF) (CWE-918)

2026-03-11 security-advisories@github.com

SSRF Plunk Useplunk

9.3

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Send crafted SNS webhook request
Exploit

Trigger SSRF in webhook handler
Execution

Server makes arbitrary HTTP GET request
Impact

Access internal resources or external targets

Vulnerability Assessment

Weakness	CWE CWE-918 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V4 - API and Web Service URL allowlisting, SSRF prevention MITRE ATT&CK 2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Plunk versions before 0.7.0 with SNS webhook handler enabled. No authentication required. Attacker must reach the SNS webhook endpoint over network; server must have outbound HTTP access to target destination.
Impact	CVSS 9.3.
Exploit ScenarioDerived	SSRF via SNS webhook.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

SSRF in Plunk email platform before 0.7.0.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:07 CVSS 9.3

SSRF in Plunk email platform.

RemediationAI

Update.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-918.

Know when Plunk gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 9.3 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

Low

Availability

None

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

Plunk email platform versions up to 0.7.0 contain a critical server-side request forgery vulnerability (CVSS 9.3) that could allow attackers to bypass security controls and access internal systems or AWS infrastructure. Any organization running affected Plunk instances faces immediate risk of data breach, lateral movement, and potential compromise of connected AWS environments.

Business Impact: Severe

Compensating Controls

Until patch availability: (1) Implement strict network segmentation isolating Plunk instances with deny-by-default outbound rules; (2) Block access to AWS metadata endpoint (169.254.169.254) at the network layer; (3) Deploy WAF rules to detect and block SSRF attack patterns including URL scheme variations and internal IP ranges; (4) Disable or restrict any Plunk features that perform external HTTP requests if configuration allows; (5) Enable enhanced logging and monitoring for all outbound requests from Plunk instances; (6) Implement API gateway authentication requiring strict request validation.

Threat Intelligence Overview

EPSS Score

0.0%

Top 88% exploitable

Data Quality

5 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

CRITICAL severity

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.