CVE-2026-129300: mail-parser · Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date
Affects parsedmarcSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 10.5.0 when convenient.
Data as of 17 Nov 2026, 18:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 10.5.0
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 parsedmarc to 10.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewparsedmarcpkg:brew/parsedmarcOther threats | 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. If upgrading is not possible, wrap all parse_from_* calls in a broad exception handler that catches all exceptions (not just MailParserError) to prevent application crashes and handle unparsed messages appropriately.
Description
mail-parser versions from 3.7.0 up to 4.6.2 have a vulnerability where an out-of-range date in the Received email header causes an uncaught OverflowError or OSError. This exception occurs outside the mail-parser exception hierarchy, causing the entire message parsing to abort. The issue affects all parsing entry points and can be triggered by attacker-controlled headers, potentially causing message loss or batch processing failures. The flaw was fixed in version 4.6.3 by catching these exceptions and setting the problematic date to null, allowing parsing to continue.
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)