CVE-2026-129295: Parsedmarc · mail-parser is vulnerable to polynomial ReDoS in email header parsing
Affects parsedmarcSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 10.4.2 soon.
Data as of 17 Nov 2026, 18:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 10.4.2
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 parsedmarc to 10.4.2.
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
A fix is available in parsedmarc mail-parser version 4.6.1, which replaces the vulnerable regexes with linear-time parsing logic and normalizes whitespace to prevent backtracking. Users should upgrade to version 4.6.1 to remediate this issue. There are no workarounds within the library. For those unable to upgrade immediately, it is recommended to cap total header size before parsing and enforce wall-clock timeouts around each parse operation.
Description
Parsedmarc's mail-parser component contains two regular expressions used in email header parsing that exhibit polynomial-time backtracking on attacker-controlled input, causing severe CPU consumption and denial of service. These vulnerabilities affect common parsing functions without requiring special input structures. The issues impact all six address headers and the Received header clause splitter, allowing small crafted emails to exhaust parsing resources. The vulnerability has been fixed in version 4.6.1 with linear-time regex replacements and whitespace normalization.
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)