CVE-2026-34975
- Source
- https://cve.org/CVERecord?id=CVE-2026-34975
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-34975.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-34975
- Aliases
-
- GHSA-2mvm-rg5v-7hfq
- Published
- 2026-04-06T16:10:05.699Z
- Modified
- 2026-07-08T08:12:56.873683835Z
- Severity
-
- 8.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N CVSS Calculator
- Summary
- Plunk has a CRLF Email Header Injection in raw MIME message construction allows authenticated API user to inject arbitrary email headers
- Details
-
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.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34975.json", "cna_assigner": "GitHub_M", "cwe_ids": [ "CWE-93" ] }- References
Affected packages
Git / github.com/useplunk/plunk
Affected ranges
- Type
- GIT
- Repo
- https://github.com/useplunk/plunk
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed
- Database specific
{ "source": [ "AFFECTED_FIELD", "CPE_RANGE" ], "cpe": "cpe:2.3:a:useplunk:plunk:*:*:*:*:*:*:*:*", "extracted_events": [ { "introduced": "0" }, { "fixed": "0.8.0" } ] }