PT-2026-148360
CVE-2026-129299
·
Published
2026-11-16
·
Updated
2026-11-16
Description by
CVSS 3.1
6.5
MediumMetricsAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Name of the Vulnerable Software and Affected Versions
mail-parser versions prior to 4.6.2
Description
Multiple message-processing issues exist where crafted emails can cause uncaught exceptions or the silent loss of content. Headers that collide with internal methods such as
Parse(), Message(), and Write Attachments() can result in bound method objects being placed into the parsed output, leading to a TypeError during JSON serialization via mail json. Additionally, when using parse from bytes(), 8-bit header values returned as email.header.Header can trigger a TypeError when passed to json.dumps through an X raw accessor.Furthermore, the software may silently discard or substitute header values if the header names contain underscores or match specific patterns like
Subject json or X Spam Flag, while the has defects flag remains false. This can be used to hide malicious indicators from downstream scanners. Additionally, messages without headers may be treated as falsy, causing the body and attachments properties to return empty values without an error signal. These issues can abort message processing or facilitate evasion.Recommendations
Update mail-parser to version 4.6.2.
As a temporary workaround for uncaught exceptions, wrap access to
mail json, mail partial json, headers json, and any X raw access in a general except Exception block instead of catching only MailParserError subclasses. Found an issue in the description? Have something to add? Feel free to write us 👾