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.

Project Subscriptions

Vendors Products
Spamscope Subscribe
Mail-parser Subscribe
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-8cgq-x343-p74c mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Thu, 19 Nov 2026 00:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 18 Nov 2026 21:30:00 +0000

Type Values Removed Values Added
First Time appeared Spamscope
Spamscope mail-parser
Vendors & Products Spamscope
Spamscope mail-parser

Wed, 18 Nov 2026 12:30:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 16 Nov 2026 18:00:00 +0000

Type Values Removed Values Added
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.
Title mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch
Weaknesses CWE-248
CWE-436
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-18T15:19:20.517Z

Reserved: 2026-11-13T22:30:18.284Z

Link: CVE-2026-129301

cve-icon Vulnrichment

Updated: 2026-11-18T15:19:14.299Z

cve-icon NVD

Status : Received

Published: 2026-11-16T18:17:31.190

Modified: 2026-11-18T16:18:10.803

Link: CVE-2026-129301

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-11-16T17:47:32Z

Links: CVE-2026-129301 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-11-18T21:09:00Z

Weaknesses