- Severity: MEDIUM
- CVE: CVE-2026-129300
- Ecosystems: pip
- Packages: mail-parser
### Impact
A `Received` header whose trailing date carries an out-of-range year, or a timezone offset
large enough to push the timestamp past the int64 epoch range, raises an exception that is
**outside the `MailParser*` hierarchy**. A caller that catches only mail-parser exceptions
does not catch it, and the parse of the entire message is aborted — the same class of issue
as [GHSA-24mq-4vc6-2prf](https://github.com/SpamScope/mail-parser/security/advisories/GHSA-24mq-4vc6-2prf),
which this survives (it is not a duplicate; 24mq is fixed in 4.6.2 and this reproduces on 4.6.2).
All entry points are affected: `parse_from_string()`, `parse_from_bytes()`, `parse_from_file()`,
`parse_from_file_obj()` and the `mail-parser` CLI. The header is fully attacker-controlled and
a single line is enough, so any pipeline that parses untrusted mail can be made to lose the
message — and, if one worker handles a queue, to drop the batch.
“`python
import mailparser
raw = (“Received: from x ([1.2.3.4]) by mx.victim.com; “
“Tue, 7 Mar 292277026596 14:29:24 +0000\r\n\r\nbody\r\n”)
mailparser.parse_from_string(raw).mail_json
# OverflowError: signed integer is greater than maximum
# 4.6.3 -> parses; the unusable hop date is reported as “date_utc”: null
“`
**Root cause.** `receiveds_format()` in `src/mailparser/utils.py` guarded the date conversion
with `except (TypeError, ValueError)`, but `convert_mail_date()` → `email.utils.mktime_tz()` →
`calendar.timegm()` raises `OverflowError` for years w…
Source: GitHub Security Advisories · 2026-11-16