mail-parser: Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date
GHSA-xhrq-2mqv-q8wx · CVE-2026-129300
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
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,
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.
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
# <= 4.6.2 -> 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 whose epoch seconds overflow int64, anddatetime.fromtimestamp() reports EOVERFLOW as OSError for a sufficiently large timezone
offset. The date and timezone properties already wrapped the same conversion inexcept Exception; only the Received path was left open.
Affected range. Introduced by the date-handling change in ca2aa6a, first released in
3.7.0. Reproduced on PyPI 3.7.0, 3.8.0, 3.9.3, 4.0.0, 4.5.0, 4.6.0, 4.6.2 and on master
before the fix (Python 3.14). 3.6.0 is not affected.
Patches
Fixed in 4.6.3. receiveds_format() now also catches OverflowError and OSError and
records date_utc = None for that hop, so the rest of the message still parses:
try:
j["date_utc"], _ = convert_mail_date(i["date"])
except (TypeError, ValueError, OverflowError, OSError):
j["date_utc"] = None
A sweep of year magnitudes from 10^7 to 10^12 shows only ValueError, OverflowError andOSError are reachable on this path.
Workarounds
Upgrade to 4.6.3. If you cannot upgrade, wrap every parse_from_* call in a bareexcept Exception rather than except MailParserError, and treat the message as unparsed.
References
References
- WEB https://github.com/SpamScope/mail-parser/security/advisories/GHSA-xhrq-2mqv-q8wx
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-129300
- WEB https://github.com/SpamScope/mail-parser/pull/171
- WEB https://github.com/SpamScope/mail-parser/commit/d69f6f9b6ad0bf74d731b373bbdeabb462c32b26
- WEB https://github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f
- PACKAGE https://github.com/SpamScope/mail-parser
- WEB https://github.com/SpamScope/mail-parser/releases/tag/4.6.3
Ready to move
Start Securing
Free, no credit card | First findings in minutes