{"answers":{"affected":"1 open source package ship an affected version, including mail-parser.","exploited":"There is no known exploitation of CVE-2026-129300 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.3 or later.","what":"CVE-2026-129300 is a medium-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-129300 and fix it if it is affected.\n\nWhat it is: CVE-2026-129300 is a medium-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-129300 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 3.7.0; fixed in 4.6.3\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-129300/ (Markdown: https://insights.sbomify.com/CVE-2026-129300/index.md)","id":"CVE-2026-129300","markdown":"https://insights.sbomify.com/CVE-2026-129300/index.md","name":"CVE-2026-129300","record":{"aliases":["GHSA-xhrq-2mqv-q8wx"],"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 crafted Received header can crash mail-parser's parse_from methods, dropping queued messages; services parsing untrusted emails should care.","user_interaction":"not_required","vuln_class":"denial_of_service","vulnerable_functions":["receiveds_format()"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 3.7.0 until 4.6.3, receiveds_format() in src/mailparser/utils.py catches only TypeError and ValueError while converting the trailing date of an attacker-controlled Received header. An out-of-range year can cause calendar.timegm() to raise OverflowError, and a sufficiently large timezone offset can cause datetime.fromtimestamp() to raise OSError. These exceptions are outside the MailParserError hierarchy, so one crafted header can abort the entire message parse through every parse_from_* entry point and may drop a queued batch. This issue is fixed in version 4.6.3.","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: Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date","id":"CVE-2026-129300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":5,"n_vendor_status":1,"next":{"headline":"mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch","id":"CVE-2026-129301"},"nickname":null,"packages":[{"ecosystem":"PyPI","fixed":["4.6.3"],"introduced":["3.7.0"],"last_affected":[],"name_kind":null,"package":"mail-parser","purl":"pkg:pypi/mail-parser","purl_source":"derived","scope":"upstream","source":"GHSA-xhrq-2mqv-q8wx"}],"prev":{"headline":"mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input","id":"CVE-2026-129299"},"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.3"],"introduced":["3.7.0"],"name":"mail-parser","purl":"pkg:pypi/mail-parser","sources":["GHSA-xhrq-2mqv-q8wx"],"status":"fixed"}],"release":null,"scope":"upstream","status":"fixed","statuses":{"fixed":1},"vendor":null}],"vendors":["SpamScope"]},"summary":"A crafted Received header can crash mail-parser's parse_from methods, dropping queued messages; services parsing untrusted emails should care.","url":"https://insights.sbomify.com/CVE-2026-129300/"}