Technical impact
From versions 4.6.0 through 4.6.2 the mail-parser library fails to isolate errors when processing MIME parts. A single malicious attachment containing a NULL byte, an overly long name, or an undecodable base64 payload triggers an exception that aborts the entire write_attachments loop. Subsequent attachments are never saved, and the error is not surfaced through the expected MailParserError path. As a result, a downstream scanner that only inspects the extraction directory may miss malicious payloads, while the aborted batch also causes a loss of functionality.
Affected Systems
The affected product is SpamScope mail-parser versions 4.6.0, 4.6.1, and 4.6.2. Version 4.6.3 includes the fix and effectively removes the flaw.
Risk and Exploitability
The CVSS score of 6.5 places the flaw in the medium severity range. No EPSS data is available, and the vulnerability is not listed in CISA KEV. An attacker who can deliver a crafted email to a system that uses mail-parser can exploit the flaw to silently drop attachments and potentially evade detection. The attack requires the ability to control the email content, which may be feasible in many mail processing environments.
Github GHSA