CVE-2026-34975— plunk 注入漏洞

Plunk has a CRLF Email Header Injection in raw MIME message construction allows authenticated API user to inject arbitrary email headers

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

对CRLF序列的转义处理不恰当(CRLF注入)

plunk 注入漏洞

plunk是Plunk开源的一个邮件发送与管理平台。 plunk 0.8.0之前版本存在注入漏洞，该漏洞源于SESService.ts中CRLF标头注入，可能导致经过身份验证的API用户注入任意电子邮件标头。

N/A

N/A