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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.8.0
Fixed in 0.8.0
Mitigation
Upgrade plunk to 0.8.0 or later.
References
- Vendor advisory github.com/useplunk/plunk/security/advisories/…
Timeline
Days relative to CVE publicationFirst public PoC 23 days after publication; not in CISA KEV. First PoC: romain-deperne/CVE-2026-34975 (created 29 Apr 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| romain-deperne/CVE-2026-34975 | 29 Apr 2026 +23 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
PoC characteristics
What to hunt for in your logs · from 1 PoC repoPOST /v1/send
- Key headers
Authorization: Bearer {var}- Body markers
"to""subject":"Test Email""body":"{var}Hello, this is a test email.</p>""from"inapplication/json- Ports
- 3000
- Seen in
- 1 repo: romain-deperne/CVE-2026-34975
- Evidence
- romain-deperne/CVE-2026-34975/poc.py:142
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/v1/send(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET [3000] (msg:"GG PoC-Monitor CVE-2026-34975 useplunk plunk exploit attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/v1/send"; http.header; content:"Authorization: Bearer "; nocase; http.request_body; content:"|22|to|22|"; http.request_body; content:"|22|subject|22|:|22|Test Email|22|"; http.request_body; content:"|22|body|22|:|22|"; http.request_body; content:"|22|from|22|"; reference:url,poc.griffinguard.io/cve/CVE-2026-34975; classtype:web-application-attack; sid:9286390; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: useplunk plunk exploit attempt (CVE-2026-34975)
id: gg-pocmon-cve-2026-34975-9286390
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-34975. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-34975
logsource:
category: webserver
detection:
selection:
cs-method: POST
cs-uri-stem|contains|all:
- '/v1/send'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2026.34975