CVE-2026-129295: Mail-parser Is Vulnerable to Polynomial ReDoS
Affects mail-parserSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 4.6.1 soon.
Data as of 16 Nov 2026, 23:12 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 4.6.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation 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.1.
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.1 or later, where the vulnerable regexes have been replaced with linear-time parsing logic and whitespace normalization. There are no workarounds within the library. Users unable to upgrade immediately should limit total header size before parsing and enforce wall-clock timeouts around parsing operations.
Description
mail-parser versions 4.2.0 through 4.6.0 are vulnerable to polynomial Regular Expression Denial of Service (ReDoS) attacks during email header parsing. Two specific regex patterns used in parsing address headers and Received headers cause excessive CPU consumption on crafted inputs with large whitespace padding, leading to denial of service. The vulnerability affects all six address headers and Received headers, allowing small emails to exhaust parsing resources. The issue is fixed in version 4.6.1.
References
- github.com/SpamScope/mail-parser/security/advisories/GHSA-r7w7-vpq8-c5vv (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-129295 (opens in a new tab)
- github.com/SpamScope/mail-parser/pull/166 (opens in a new tab)
- github.com/SpamScope/mail-parser/commit/037293158cb291caa96635a54449243d32cd4d96 (opens in a new tab)
- github.com/SpamScope/mail-parser/commit/5aab122f0d763991604d2c2bcc807c6bf2489464 (opens in a new tab)
- github.com/SpamScope/mail-parser/commit/85e53f820d78ae7c955dafbbcd0e20989a735c2c (opens in a new tab)
- github.com/SpamScope/mail-parser (opens in a new tab)
- github.com/SpamScope/mail-parser/releases/tag/4.6.1 (opens in a new tab)