{"answers":{"affected":"2 open source packages ship an affected version, including Haraka. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34752 exists.","fix":"Upgrade Haraka to 3.1.4 or later.","what":"CVE-2026-34752 is a high-severity denial of service vulnerability in Haraka, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34752 and fix it if it is affected.\n\nWhat it is: CVE-2026-34752 is a high-severity denial of service vulnerability in Haraka, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34752 exists.\n\nAffected packages and fixed versions:\n- Haraka (npm): affected all versions; fixed in 3.1.4\n- Haraka (npm): affected all versions; fixed in 3.1.4\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-34752/ (Markdown: https://insights.sbomify.com/CVE-2026-34752/index.md)","id":"CVE-2026-34752","markdown":"https://insights.sbomify.com/CVE-2026-34752/index.md","name":"CVE-2026-34752","record":{"aliases":["GHSA-xph3-r2jf-4vp3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js mail server","requires_auth":"none","summary":"An attacker can crash the Haraka mail server worker process by sending an email with a specific header, requiring a patch to restore service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"haraka","vendor":"haraka_project"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"Haraka is a Node.js mail server. Prior to version 3.1.4, sending an email with __proto__: as a header name crashes the Haraka worker process. This issue has been patched in version 3.1.4.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Haraka affected by DoS via `__proto__` email header","id":"CVE-2026-34752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"vLLM affected by Server-Side Request Forgery (SSRF) in `download_bytes_from_url `","id":"CVE-2026-34753"},"packages":[{"ecosystem":"npm","fixed":["3.1.4"],"introduced":["0"],"last_affected":[],"package":"Haraka","purl":null,"source":"GHSA-xph3-r2jf-4vp3"},{"ecosystem":"npm","fixed":["3.1.4"],"introduced":["0"],"last_affected":[],"package":"Haraka","purl":"pkg:npm/Haraka","source":"GHSA-xph3-r2jf-4vp3"}],"prev":{"headline":"Payload has Unvalidated Input in Password Recovery Endpoints","id":"CVE-2026-34751"},"products":["Haraka"],"published":"2026-04-02","related":[{"cvss_score":9.8,"headline":"Critical severity vulnerability that affects Haraka","id":"CVE-2016-1000282","kev_date_added":null,"published":"2019-02-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-03","vendors":["haraka"]},"summary":"An attacker can crash the Haraka mail server worker process by sending an email with a specific header, requiring a patch to restore service.","url":"https://insights.sbomify.com/CVE-2026-34752/"}