{"api_version":"1","generated_at":"2026-11-16T19:35:18+00:00","cve":"CVE-2026-129301","urls":{"html":"https://cve.report/CVE-2026-129301","api":"https://cve.report/api/cve/CVE-2026-129301.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-129301","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-129301"},"summary":{"title":"mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch","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.6.0 until 4.6.3, write_attachments() calls _safe_attachment_filename() and write_sample() without isolating failures for individual attacker-controlled MIME parts. An RFC 2231 filename containing a NUL, a basename exceeding NAME_MAX, or an undecodable base64 payload can raise ValueError, OSError, or binascii.Error and abort the entire save loop. Later attachments remain unwritten; when a caller catches only MailParserError, the failure is not surfaced through the expected library-exception path. If a downstream scanner or sandbox reads only the extraction directory, a payload after the crafted part can be missed even though it remains in the delivered message, and the aborted batch also causes availability loss. This issue is fixed in version 4.6.3.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-11-16 18:17:31","updated_at":"2026-11-16 18:17:31"},"problem_types":["CWE-248","CWE-436","CWE-248 CWE-248: Uncaught Exception","CWE-436 CWE-436: Interpretation Conflict"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"6.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"LOW","availabilityImpact":"LOW"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"6.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","data":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"}}],"references":[{"url":"https://github.com/SpamScope/mail-parser/pull/171","name":"https://github.com/SpamScope/mail-parser/pull/171","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f","name":"https://github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/SpamScope/mail-parser/commit/11b894a0b8b3f11055a99caff118206138d1daba","name":"https://github.com/SpamScope/mail-parser/commit/11b894a0b8b3f11055a99caff118206138d1daba","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/SpamScope/mail-parser/security/advisories/GHSA-8cgq-x343-p74c","name":"https://github.com/SpamScope/mail-parser/security/advisories/GHSA-8cgq-x343-p74c","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/SpamScope/mail-parser/releases/tag/4.6.3","name":"https://github.com/SpamScope/mail-parser/releases/tag/4.6.3","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-129301","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-129301","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"SpamScope","product":"mail-parser","version":"affected >= 4.6.0, < 4.6.3","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"product":"mail-parser","vendor":"SpamScope","versions":[{"status":"affected","version":">= 4.6.0, < 4.6.3"}]}],"descriptions":[{"lang":"en","value":"mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.6.0 until 4.6.3, write_attachments() calls _safe_attachment_filename() and write_sample() without isolating failures for individual attacker-controlled MIME parts. An RFC 2231 filename containing a NUL, a basename exceeding NAME_MAX, or an undecodable base64 payload can raise ValueError, OSError, or binascii.Error and abort the entire save loop. Later attachments remain unwritten; when a caller catches only MailParserError, the failure is not surfaced through the expected library-exception path. If a downstream scanner or sandbox reads only the extraction directory, a payload after the crafted part can be missed even though it remains in the delivered message, and the aborted batch also causes availability loss. This issue is fixed in version 4.6.3."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"LOW","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"LOW","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-248","description":"CWE-248: Uncaught Exception","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-436","description":"CWE-436: Interpretation Conflict","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-16T17:47:32.676Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/SpamScope/mail-parser/security/advisories/GHSA-8cgq-x343-p74c","tags":["x_refsource_CONFIRM"],"url":"https://github.com/SpamScope/mail-parser/security/advisories/GHSA-8cgq-x343-p74c"},{"name":"https://github.com/SpamScope/mail-parser/pull/171","tags":["x_refsource_MISC"],"url":"https://github.com/SpamScope/mail-parser/pull/171"},{"name":"https://github.com/SpamScope/mail-parser/commit/11b894a0b8b3f11055a99caff118206138d1daba","tags":["x_refsource_MISC"],"url":"https://github.com/SpamScope/mail-parser/commit/11b894a0b8b3f11055a99caff118206138d1daba"},{"name":"https://github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f","tags":["x_refsource_MISC"],"url":"https://github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f"},{"name":"https://github.com/SpamScope/mail-parser/releases/tag/4.6.3","tags":["x_refsource_MISC"],"url":"https://github.com/SpamScope/mail-parser/releases/tag/4.6.3"}],"source":{"advisory":"GHSA-8cgq-x343-p74c","discovery":"UNKNOWN"},"title":"mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-129301","datePublished":"2026-11-16T17:47:32.676Z","dateReserved":"2026-11-13T22:30:18.284Z","dateUpdated":"2026-11-16T17:47:32.676Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-16 18:17:31","lastModifiedDate":"2026-11-16 18:17:31","problem_types":["CWE-248","CWE-436","CWE-248 CWE-248: Uncaught Exception","CWE-436 CWE-436: Interpretation Conflict"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"LOW","availabilityImpact":"LOW"},"exploitabilityScore":3.9,"impactScore":2.5}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"129301","Ordinal":"1","Title":"mail-parser: One hostile attachment aborts `write_attachments()`","CVE":"CVE-2026-129301","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"129301","Ordinal":"1","NoteData":"mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.6.0 until 4.6.3, write_attachments() calls _safe_attachment_filename() and write_sample() without isolating failures for individual attacker-controlled MIME parts. An RFC 2231 filename containing a NUL, a basename exceeding NAME_MAX, or an undecodable base64 payload can raise ValueError, OSError, or binascii.Error and abort the entire save loop. Later attachments remain unwritten; when a caller catches only MailParserError, the failure is not surfaced through the expected library-exception path. If a downstream scanner or sandbox reads only the extraction directory, a payload after the crafted part can be missed even though it remains in the delivered message, and the aborted batch also causes availability loss. This issue is fixed in version 4.6.3.","Type":"Description","Title":"mail-parser: One hostile attachment aborts `write_attachments()`"}]}}}