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

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

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **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:** Yes
- **Published:** 16 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-xhrq-2mqv-q8wx

## 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 (Uncaught Exception)

## 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.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `mail-parser` | PyPI | `pkg:pypi/mail-parser` | From 3.7.0 | 4.6.3 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `mail-parser` | 4.6.3 |

## How do I fix CVE-2026-129300?

Upgrade mail-parser to 4.6.3 or later.

## Is CVE-2026-129300 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129300 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-129300 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected packages and fixed versions:
- mail-parser (PyPI): affected from 3.7.0; fixed in 4.6.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129300/ (Markdown: https://insights.sbomify.com/CVE-2026-129300/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129300
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129300
- OSV: https://osv.dev/vulnerability/CVE-2026-129300

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129300/
Summaries are generated and may contain mistakes; the official description above is the record.
