CVE-2026-129295
mail-parser is vulnerable to polynomial ReDoS in email header parsing
No exploitation reported by the sources we read.
- Published2026-11-16
- Fixed in4.6.1
- WeaknessCWE-1333
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
mail-parser is a tool that parses emails by enhancing the Python standard library and extracting message details into a comprehensive object. From 4.2.0 until 4.6.1, attacker-controlled email headers can cause polynomial regular-expression backtracking during ordinary parse_from_string(), parse_from_bytes(), or parse_from_file() calls. In src/mailparser/utils.py, get_addresses() invokes the _ADDR_FALLBACK_RE fallback when strict address parsing yields no usable address, and overlapping quantifiers rescan padded address headers quadratically or cubically. In src/mailparser/const.py, parse_received() applies _CLAUSE_SPLITTER to uncollapsed whitespace in a Received header, causing quadratic backtracking when a whitespace run is not followed by a clause keyword. A small, well-formed message can keep mail gateway, ticketing, quarantine, or archival parsing workers busy for extended periods. This issue is fixed in version 4.6.1.
Timeline
dates in UTC- 2026-11-1617:32CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.x | ≥ 4.2.0, < 4.6.1 | 4.6.1 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- SpamScope mail-parserAffected
- = >= 4.2.0, < 4.6.1no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-16
Fix
- Update mail-parser to 4.6.1
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
- CNACVSS 3.17.52026-11-16
- CNAweakness (CWE)CWE-13332026-11-16
- NVDweakness (CWE)CWE-1333read 2026-11-16
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2026-11-16
Identifiers
- EUVD-2026-126570same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-r7w7-vpq8-c5vvsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2026-11-16
- Last Modified
- 2026-11-16
- NVD status
- Received
- GitHub Advisory
- GHSA-r7w7-vpq8-c5vv
Frequently asked questions
What is CVE-2026-129295?
Is CVE-2026-129295 actively exploited?
What is the CVSS score for CVE-2026-129295?
Running mail-parser? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-r7w7-vpq8-c5vv
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served