{"answers":{"affected":"1 open source package ship an affected version, including mail-parser.","exploited":"There is no known exploitation of CVE-2026-129296 in the wild and no public exploit code.","exposure":"An affected version is only exploitable if your software calls write_attachments() or write_sample(). Many projects that include it are not exposed.","fix":"Upgrade mail-parser to 4.6.0 or later.","what":"CVE-2026-129296 is a medium-severity path traversal vulnerability in SpamScope mail-parser, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-129296 and fix it if it is affected.\n\nWhat it is: CVE-2026-129296 is a medium-severity path traversal vulnerability in SpamScope mail-parser, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-129296 in the wild and no public exploit code.\nExposure: An affected version is only exploitable if your software calls write_attachments() or write_sample(). Many projects that include it are not exposed.\n\nAffected packages and fixed versions:\n- mail-parser (PyPI): affected from 3.8.0; fixed in 4.6.0\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.\n   If an affected version is present, also search the code for calls to write_attachments() or write_sample() and report whether any exist.\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-129296/ (Markdown: https://insights.sbomify.com/CVE-2026-129296/index.md)","id":"CVE-2026-129296","markdown":"https://insights.sbomify.com/CVE-2026-129296/index.md","name":"CVE-2026-129296","record":{"aliases":["GHSA-fr3h-cpq2-9496"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Python email parser","requires_auth":"none","requires_specific_call":true,"summary":"Crafted email attachments can make mail-parser write files outside the output directory, overwriting files in applications extracting attachments.","user_interaction":"required","vuln_class":"path_traversal","vulnerable_functions":["write_attachments()","write_sample()"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.8.0 until 4.6.0, the write_attachments() and write_sample() APIs use attacker-controlled attachment filenames without sufficient sanitization and path containment validation. Directory traversal sequences and absolute filesystem paths can cause an attachment to be written outside the intended output directory. An attacker can overwrite files accessible to the parsing process when an application extracts attachments from a crafted message. This issue is fixed in version 4.6.0.","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: Path Traversal vulnerability in attachment extraction","id":"CVE-2026-129296","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":1,"n_references":5,"n_vendor_status":1,"next":{"headline":"mail-parser: Sender IP address spoofing in `get_server_ipaddress()","id":"CVE-2026-129297"},"nickname":null,"packages":[{"ecosystem":"PyPI","fixed":["4.6.0"],"introduced":["3.8.0"],"last_affected":[],"name_kind":null,"package":"mail-parser","purl":"pkg:pypi/mail-parser","purl_source":"derived","scope":"upstream","source":"GHSA-fr3h-cpq2-9496"}],"prev":{"headline":"mail-parser is vulnerable to polynomial ReDoS in email header parsing","id":"CVE-2026-129295"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-16","vendor_status":[{"n_packages":1,"name":"Upstream","packages":[{"fixed":["4.6.0"],"introduced":["3.8.0"],"name":"mail-parser","purl":"pkg:pypi/mail-parser","sources":["GHSA-fr3h-cpq2-9496"],"status":"fixed"}],"release":null,"scope":"upstream","status":"fixed","statuses":{"fixed":1},"vendor":null}],"vendors":["SpamScope"]},"summary":"Crafted email attachments can make mail-parser write files outside the output directory, overwriting files in applications extracting attachments.","url":"https://insights.sbomify.com/CVE-2026-129296/"}