Medium

mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input

  • Disclosed: 16.11.2026
  • Updated: 17.11.2026 01:17

Impact

Two effects, sharing the root cause of Advisory 1 — header names chosen by the sender were resolved through Python attribute lookup and rewritten before lookup.

Uncaught exceptions. A crafted message raises an exception that is outside the MailParser* hierarchy, so a caller catching only mail-parser exceptions does not catch it and the worker dies.

Header named after a method (CWE-248, reported by @iam-niranjan). Python resolves real class attributes before __getattr__, so a header named after a method put a bound method object into the parsed mail dict. A 12-byte email is sufficient. Nine colliding names were confirmed: Parse, Message, Write_Attachments, From_File, From_File_Obj, From_File_Msg, From_String, From_Bytes, Get_Server_Ipaddress. Also reproducible from the CLI (mail-parser -f evil.eml -j).

python
import mailparser
mailparser.parse_from_string("Parse: x\r\n\r\n").mail_json
# 4.6.1 -> TypeError: Object of type method is not JSON serializable
# 4.6.2 -> {"parse": "x", "has_defects": false}

Header carrying 8-bit bytes (CWE-248). For a header containing raw 8-bit bytes, Python's compat32 policy returns an email.header.Header rather than a str, which the _raw accessor passed straight to json.dumps. This fires on entirely benign non-ASCII mail via parse_from_bytes(), the normal entry point for mail off the wire.

python
import mailparser
mailparser.parse_from_bytes(b"Subject: caf\xe9\r\n\r\nbody\r\n").subject_raw
# 4.6.1 -> TypeError: Object of type Header is not JSON serializable
# 4.6.2 -> '["caf�"]'

Silent loss of message content (CWE-436). A sender can make a header's value vanish from every output surface, or be replaced by a different header's value, with has_defects remaining false. This is an evasion primitive: the tool's output diverges from the bytes actually in the message, and a pipeline scanning parsed output for indicators sees nothing and no failure signal.

Header names were normalised before lookup — underscores folded to dashes, and _json / _raw suffixes interpreted — so a header genuinely named Subject_json was reported with the value of Subject and its own value discarded, and any header whose name contains an underscore resolved to nothing.

python
import mailparser

raw = ("From: Real Sender <real@good.example>\r\n"
       "Subject: innocuous\r\n"
       "Subject_json: MALWARE-C2 http://evil.example/payload.exe\r\n"
       "X_Spam_Flag: YES\r\n\r\nbody\r\n")
mail = mailparser.parse_from_string(raw)
print(mail.mail["subject_json"])       # 4.6.1 -> '"innocuous"'   4.6.2 -> the real value
print(mail.headers["X_Spam_Flag"])     # 4.6.1 -> ''              4.6.2 -> 'YES'
print("MALWARE-C2" in mail.mail_json)  # 4.6.1 -> False           4.6.2 -> True
print(mail.has_defects)                # both  -> False

A related case: email.message.Message.__len__ returns the header count, so a message with no headers is falsy. parse() returned before initialising state, and the unset attributes were then absorbed by __getattr__ and answered as absent headers. Every property returned '' — including mail and attachments, which are documented to return a dict and a list — with no error and no defect flag.

python
import mailparser
mail = mailparser.parse_from_string("Click http://evil.example/pay.exe now\r\n")
print(repr(mail.body))         # 4.6.1 -> ''    4.6.2 -> the text
print(repr(mail.attachments))  # 4.6.1 -> ''    4.6.2 -> []
print(mail.has_defects)        # 4.6.1 -> ''    4.6.2 -> True

Patches

Fixed in 4.6.2. Upgrade with pip install --upgrade mail-parser.

Header names taken from a message are now looked up literally — no attribute access, no case or separator folding, no suffix interpretation — so no header name can collide with a method or property, and no value can be substituted or dropped. 8-bit values are coerced to str before serialisation. Parser state is initialised before the message check, which now tests is None, and attribute names beginning with _ raise AttributeError instead of being answered as headers.

Behaviour changes. Header names now appear in mail and headers exactly as sent, so a header named X_Spam_Flag keeps that name and its own value. X_raw always returns a JSON array — an absent header yields [] where 4.6.1 returned null.

Workarounds

None for the data loss. For the uncaught exceptions, callers who cannot upgrade should wrap mail_json, mail_partial_json, headers_json and any X_raw access in a bare except Exception rather than catching only MailParserError subclasses.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) mail-parser < 4.6.2 4.6.2

References

CVSS score 6.5/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Weakness (CWE)
CWE-248, CWE-436
Platform
Python (PyPI)
Package
mail-parser
Disclosed
16.11.2026
Updated
17.11.2026 01:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-24mq-4vc6-2prf - CC BY 4.0

Vulnerability history: mail-parser

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
6
First → latest
11.2026 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 2
  • Medium 4

Disclosures per year

  1. 2026: 6
  1. Medium · 5.3 CVE-2026-129300 >= 3.7.0, < 4.6.3 4.6.3
  2. mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input this entry
    Medium · 6.5 CVE-2026-129299 < 4.6.2 4.6.2
  3. High · 7.5 CVE-2026-129297 < 4.6.2 4.6.2
  4. High · 7.5 CVE-2026-129295 >= 4.2.0, < 4.6.1 4.6.1
  5. Medium · 6.5 CVE-2026-129296 >= 3.8.0, < 4.6.0 4.6.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.