CVE-2026-129300 mail-parser: Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date

Medium 5.3 Published Updated

A crafted Received header can crash mail-parser's parse_from methods, dropping queued messages; services parsing untrusted emails should care.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Harmful if only installed
No
Needs a specific call
No
Fix
Available

What is CVE-2026-129300?

CVE-2026-129300 is a medium-severity denial of service vulnerability in SpamScope mail-parser, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 3.7.0 until 4.6.3, receiveds_format() in src/mailparser/utils.py catches only TypeError and ValueError while converting the trailing date of an attacker-controlled Received header. An out-of-range year can cause calendar.timegm() to raise OverflowError, and a sufficiently large timezone offset can cause datetime.fromtimestamp() to raise OSError. These exceptions are outside the MailParserError hierarchy, so one crafted header can abort the entire message parse through every parse_from_* entry point and may drop a queued batch. This issue is fixed in version 4.6.3.

Weakness: CWE-248

Which versions are affected by CVE-2026-129300?

1 open source package ship an affected version, including mail-parser.

An affected version is exposed as installed. No special setting or call is needed.

PackageAffectedFixed in
mail-parser PyPI
pkg:pypi/mail-parser
From 3.7.04.6.3
Status by vendor (1)
WhoReleaseStatusPackages
Upstreamfixedmail-parser (4.6.3)

How do I fix CVE-2026-129300?

Upgrade mail-parser to 4.6.3 or later.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-129300 being exploited?

There is no known exploitation of CVE-2026-129300 in the wild and no public exploit code.

Sources

Also known as GHSA-xhrq-2mqv-q8wx.

Is CVE-2026-129300 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free