{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34975 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34975 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34975 is a high-severity vulnerability in useplunk plunk, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34975 and fix it if it is affected.\n\nWhat it is: CVE-2026-34975 is a high-severity vulnerability in useplunk plunk, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34975 in the wild and no public exploit code.\n\nAffected product: useplunk plunk. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34975/ (Markdown: https://insights.sbomify.com/CVE-2026-34975/index.md)","id":"CVE-2026-34975","markdown":"https://insights.sbomify.com/CVE-2026-34975/index.md","name":"CVE-2026-34975","record":{"aliases":["GHSA-2mvm-rg5v-7hfq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Email platform","requires_auth":"low_privilege","summary":"Authenticated users can inject arbitrary email headers via CRLF characters in Plunk, enabling sender spoofing and silent forwarding.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"plunk","vendor":"useplunk"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-04-29","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-29T21:16:41Z","kind":"github_poc","ref":"https://github.com/romain-deperne/CVE-2026-34975","stars":0,"title":"CRLF email header injection in Plunk raw MIME construction — CVE-2026-34975 / CVSS 8.5"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Other in plunk","id":"CVE-2026-34975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Dgraph Affected by Pre-Auth Database Overwrite + SSRF + File Read via restoreTenant Missing Authorization","id":"CVE-2026-34976"},"packages":[],"prev":{"headline":"phpMyFAQ: SVG Sanitizer Bypass via HTML Entity Encoding leads to Stored XSS and Privilege Escalation","id":"CVE-2026-34974"},"products":["plunk"],"published":"2026-04-06","related":[{"cvss_score":9.3,"headline":"Plunk has SSRF via unvalidated AWS SNS SubscriptionConfirmation in POST /webhooks/sns","id":"CVE-2026-32096","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":5.4,"headline":"Plunk has Stored Cross-Site Scripting (XSS) via SVG File Upload","id":"CVE-2026-32095","kev_date_added":null,"published":"2026-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["useplunk"]},"summary":"Authenticated users can inject arbitrary email headers via CRLF characters in Plunk, enabling sender spoofing and silent forwarding.","url":"https://insights.sbomify.com/CVE-2026-34975/"}