CVE-2026-34975: fallo de gravedad alta en useplunk plunk
Plunk has a CRLF Email Header Injection in raw MIME message construction allows authenticated API user to inject arbitrary email headers
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 8.5epss 0.2%
Plunk is an open-source email platform built on top of AWS SES. Prior to 0.8.0, a CRLF header injection vulnerability was discovered in SESService.ts, where user-supplied values for from.name, subject, custom header keys/values, and attachment filenames were interpolated directly into raw MIME messages without sanitization. An authenticated API user could inject arbitrary email headers (e.g. Bcc, Reply-To) by embedding carriage return/line feed characters in these fields, enabling silent email forwarding, reply redirection, or sender spoofing. The fix adds input validation at the schema level to reject any of these fields containing \r or \n characters, consistent with the existing validation already applied to the contentId field. This vulnerability is fixed in 0.8.0.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Productos afectados
useplunk · plunkCVEs relacionadas — useplunk plunk
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-32096CRITICALPlunk has SSRF via unvalidated AWS SNS SubscriptionConfirmation in POST /webhooks/snsEPSS 0.3%CVE-2026-42192MEDIUMPlunk: Stored XSS in campaign viewEPSS 0.2%CVE-2026-32095MEDIUMPlunk has Stored Cross-Site Scripting (XSS) via SVG File UploadEPSS 0.2%CVE-2026-42193CRITICALPlunk: SNS webhook forgeryEPSS 0.1%