{"answers":{"affected":"1 open source package ship an affected version, including mail-parser.","exploited":"There is no known exploitation of CVE-2026-129295 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"Upgrade mail-parser to 4.6.1 or later.","what":"CVE-2026-129295 is a high-severity denial of service vulnerability in SpamScope mail-parser, published on 16 Nov 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-129295 and fix it if it is affected.\n\nWhat it is: CVE-2026-129295 is a high-severity denial of service vulnerability in SpamScope mail-parser, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-129295 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected packages and fixed versions:\n- mail-parser (PyPI): affected from 4.2.0; fixed in 4.6.1\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-129295/ (Markdown: https://insights.sbomify.com/CVE-2026-129295/index.md)","id":"CVE-2026-129295","markdown":"https://insights.sbomify.com/CVE-2026-129295/index.md","name":"CVE-2026-129295","record":{"aliases":["GHSA-r7w7-vpq8-c5vv"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python email parser","requires_auth":"none","requires_specific_call":false,"summary":"A small crafted email with malicious headers can trigger quadratic regex backtracking in mail-parser, hanging mail gateways or ticketing workers.","user_interaction":"not_required","vuln_class":"denial_of_service","vulnerable_functions":["parse_from_string","parse_from_bytes","parse_from_file"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.2.0 until 4.6.1, attacker-controlled email headers can cause polynomial regular-expression backtracking during ordinary parse_from_string(), parse_from_bytes(), or parse_from_file() calls. In src/mailparser/utils.py, get_addresses() invokes the _ADDR_FALLBACK_RE fallback when strict address parsing yields no usable address, and overlapping quantifiers rescan padded address headers quadratically or cubically. In src/mailparser/const.py, parse_received() applies _CLAUSE_SPLITTER to uncollapsed whitespace in a Received header, causing quadratic backtracking when a whitespace run is not followed by a clause keyword. A small, well-formed message can keep mail gateway, ticketing, quarantine, or archival parsing workers busy for extended periods. This issue is fixed in version 4.6.1.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mail-parser is vulnerable to polynomial ReDoS in email header parsing","id":"CVE-2026-129295","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":6,"n_vendor_status":1,"next":{"headline":"mail-parser: Path Traversal vulnerability in attachment extraction","id":"CVE-2026-129296"},"nickname":null,"packages":[{"ecosystem":"PyPI","fixed":["4.6.1"],"introduced":["4.2.0"],"last_affected":[],"name_kind":null,"package":"mail-parser","purl":"pkg:pypi/mail-parser","purl_source":"derived","scope":"upstream","source":"GHSA-r7w7-vpq8-c5vv"}],"prev":{"headline":"N-central SIS repository file parsers XML external entity injection","id":"CVE-2026-129287"},"products":["mail-parser"],"published":"2026-11-16","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-17","vendor_status":[{"n_packages":1,"name":"Upstream","packages":[{"fixed":["4.6.1"],"introduced":["4.2.0"],"name":"mail-parser","purl":"pkg:pypi/mail-parser","sources":["GHSA-r7w7-vpq8-c5vv"],"status":"fixed"}],"release":null,"scope":"upstream","status":"fixed","statuses":{"fixed":1},"vendor":null}],"vendors":["SpamScope"]},"summary":"A small crafted email with malicious headers can trigger quadratic regex backtracking in mail-parser, hanging mail gateways or ticketing workers.","url":"https://insights.sbomify.com/CVE-2026-129295/"}