CVE-2026-129299 mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input
- Published
- Updated
- Exploit status
- No public exploit known
Description
mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. Prior to 4.6.2, multiple message-processing behaviors can raise exceptions or silently lose content. Headers colliding with methods such as Parse, Message, and Write_Attachments can place bound method objects into parsed output and raise TypeError when a caller requests JSON serialization such as mail_json. When byte input is parsed through parse_from_bytes(), an 8-bit header value returned as email.header.Header can likewise raise TypeError when an X_raw accessor passes the value to json.dumps; both exceptions are outside the MailParserError hierarchy. Separately, rewritten names such as Subject_json and X_Spam_Flag can be substituted or disappear from mail, headers, and JSON output while has_defects remains false, and a headerless message can be treated as falsy before parser state is initialized, causing body and attachment properties to return empty values without an error signal. These behaviors can abort message processing or hide malicious indicators from downstream scanners. This issue is fixed in version 4.6.2.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| SpamScope mail-parser | = < 4.6.2 | No fix listed |
| pypi mail-parser(PyPI) | <= 4.6.1 | No fix listed |
| pypi mail-parser(PyPI) | < 4.6.2 | 4.6.2 |
| pypi mail-parser(PyPI) | = 0.5.0 | No fix listed |
| pypi mail-parser(PyPI) | = 1.0.0 | No fix listed |
| pypi mail-parser(PyPI) | = 1.0.0rc1 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.0 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.1 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.10 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.2 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.3 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.4 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.5 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.6 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.7 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.8 | No fix listed |
| pypi mail-parser(PyPI) | = 1.1.9 | No fix listed |
| pypi mail-parser(PyPI) | = 1.2.0 | No fix listed |
| pypi mail-parser(PyPI) | = 1.2.1 | No fix listed |
| pypi mail-parser(PyPI) | = 1.2.2 | No fix listed |
| pypi mail-parser(PyPI) | = 1.2.4 | No fix listed |
| pypi mail-parser(PyPI) | = 1.2.5 | No fix listed |
| pypi mail-parser(PyPI) | = 1.2.6 | No fix listed |
| pypi mail-parser(PyPI) | = 2.0.0 | No fix listed |
| pypi mail-parser(PyPI) | = 2.0.1 | No fix listed |
Show 47 more
| Product | Affected versions | Fixed in |
|---|---|---|
| pypi mail-parser(PyPI) | = 2.1.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.0.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.1.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.10.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.11.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.12.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.13.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.14.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.15.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.2.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.2.1 | No fix listed |
| pypi mail-parser(PyPI) | = 3.2.2 | No fix listed |
| pypi mail-parser(PyPI) | = 3.2.3 | No fix listed |
| pypi mail-parser(PyPI) | = 3.2.4 | No fix listed |
| pypi mail-parser(PyPI) | = 3.2.5 | No fix listed |
| pypi mail-parser(PyPI) | = 3.2.6 | No fix listed |
| pypi mail-parser(PyPI) | = 3.2.7 | No fix listed |
| pypi mail-parser(PyPI) | = 3.3.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.3.1 | No fix listed |
| pypi mail-parser(PyPI) | = 3.3.2 | No fix listed |
| pypi mail-parser(PyPI) | = 3.3.3 | No fix listed |
| pypi mail-parser(PyPI) | = 3.4.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.4.1 | No fix listed |
| pypi mail-parser(PyPI) | = 3.5.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.5.1 | No fix listed |
| pypi mail-parser(PyPI) | = 3.6.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.6.1 | No fix listed |
| pypi mail-parser(PyPI) | = 3.7.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.7.1 | No fix listed |
| pypi mail-parser(PyPI) | = 3.8.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.8.1 | No fix listed |
| pypi mail-parser(PyPI) | = 3.9.0 | No fix listed |
| pypi mail-parser(PyPI) | = 3.9.1 | No fix listed |
| pypi mail-parser(PyPI) | = 3.9.2 | No fix listed |
| pypi mail-parser(PyPI) | = 3.9.3 | No fix listed |
| pypi mail-parser(PyPI) | = 4.0.0 | No fix listed |
| pypi mail-parser(PyPI) | = 4.1.0 | No fix listed |
| pypi mail-parser(PyPI) | = 4.1.2 | No fix listed |
| pypi mail-parser(PyPI) | = 4.1.3 | No fix listed |
| pypi mail-parser(PyPI) | = 4.1.4 | No fix listed |
| pypi mail-parser(PyPI) | = 4.2.0 | No fix listed |
| pypi mail-parser(PyPI) | = 4.2.1 | No fix listed |
| pypi mail-parser(PyPI) | = 4.3.0 | No fix listed |
| pypi mail-parser(PyPI) | = 4.4.0 | No fix listed |
| pypi mail-parser(PyPI) | = 4.5.0 | No fix listed |
| pypi mail-parser(PyPI) | = 4.6.0 | No fix listed |
| pypi mail-parser(PyPI) | = 4.6.1 | No fix listed |
References
- https://github.com/SpamScope/mail-parser/security/advisories/GHSA-24mq-4vc6-2prf vendor-advisory
- https://github.com/SpamScope/mail-parser/pull/167 patch
- https://github.com/SpamScope/mail-parser/commit/ce3cf3559db1ff806bda598b378de9f8c2a5be96 patch
- https://github.com/SpamScope/mail-parser/releases/tag/4.6.2
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com
- github.com product
- Debian Security Tracker CVE-2026-129299 vendor-advisory