CVE-2026-129300: mail-parser · Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date
Affects mail-parserSource GCVE Database
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
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.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:LExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| PyPImail-parser | Affected
| Fixed in
|
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
- github.com/SpamScope/mail-parser/security/advisories/GHSA-xhrq-2mqv-q8wx (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129300 (opens in a new tab)
- github.com/SpamScope/mail-parser/pull/171 (opens in a new tab)
- github.com/SpamScope/mail-parser/commit/d69f6f9b6ad0bf74d731b373bbdeabb462c32b26 (opens in a new tab)
- github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f (opens in a new tab)
- github.com/SpamScope/mail-parser (opens in a new tab)
- github.com/SpamScope/mail-parser/releases/tag/4.6.3 (opens in a new tab)