Intel

AIKIDO-2026-150275

mail-parser is vulnerable to Interpretation Conflict

Interpretation ConflictGHSA-24mq-4vc6-2prf Published Aug 14, 2026

65

Medium Risk

This Affects:

PYTHONmail-parser
3.0.0 - 4.6.1
Fixed in 4.6.2
Are you affected? Scan for Free

TL;DR

Sender-chosen header names are resolved through Python attribute lookup and rewritten before lookup, folding underscores to dashes and interpreting _json and _raw suffixes. A header named after a class method or carrying raw 8-bit bytes raises an exception outside the MailParser error hierarchy, so callers catching only library errors let the worker die, and header values can be silently dropped or replaced by another header's value while has_defects stays false, giving a detection-evasion primitive. The parsed output then diverges from the bytes actually present in the message. The fix looks up header names literally without attribute access or suffix interpretation, coerces 8-bit values to text before serialization, and initializes parser state before the message check.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and parse untrusted email with this library.

Background info

mail-parser is vulnerable to Interpretation Conflict in versions 3.0.0 - 4.6.1.

How to fix this

Upgrade the mail-parser library to the patch version.