Skip to main content
VulnerabilityPublished

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

Affects mail-parserSource GCVE Database

0
Compare
Authoritative record:CVE-2026-129300· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.6.3 when convenient.

Data as of 17 Nov 2026, 00:04 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.3
Patch
Available – fixed in 4.6.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade mail-parser to 4.6.3.

Affected software

ProductAffectedFixed in
PyPImail-parserAffected
  • >=3.7.0 <4.6.3
Fixed in
  • 4.6.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade mail-parser to version 4.6.3 or later, where the issue is fixed by proper exception handling. If upgrading is not possible, wrap all parse_from_* calls in a broad except Exception handler instead of only catching MailParserError, and treat the message as unparsed if an exception occurs.

Description

mail-parser versions from 3.7.0 up to but not including 4.6.3 contain a vulnerability where an out-of-range year or large timezone offset in a Received header date causes an uncaught OverflowError or OSError. This exception occurs outside the mail-parser exception hierarchy, causing the entire message parsing to abort if the caller only catches mail-parser exceptions. The issue was fixed in version 4.6.3 by catching these exceptions and setting the problematic date to null, allowing the rest of the message to parse.

References

Community reviews

Loading reviews…