CVE
mail-parser denial of service in email header parsing
Affects mail-parser 4.2.0 up to but not including 4.6.1, via the address-header fallback in email header parsing. Fixed in 4.6.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 4.6.1
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The SpamScope mail-parser Python library can be forced into excessive processing when parsing attacker-controlled email headers. A remote attacker can trigger this without logging in by sending a small, well-formed message, which can keep mail gateway, ticketing, quarantine, or archival parsing workers busy for extended periods.
Original 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.
Who should check
Teams running mail-parser 4.2.0 through 4.6.0 that parse untrusted email, such as mail gateways, ticketing systems, quarantine UIs, or archiving pipelines.
“>= 4.2.0, < 4.6.1”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 4.6.1.
Workaround: Cap total header size before parsing and enforce a wall-clock timeout around each parse.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129295 (mail-parser is vulnerable to polynomial ReDoS in email header parsing), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129295 (entry last updated 2026-11-16):
Affected:
- SpamScope mail-parser: from 4.2.0, fixed in 4.6.1
Fixed versions: 4.6.1.
Conditions (all must be true for the bug to be hit):
- Affected versions of mail-parser from 4.2.0 up to but not including 4.6.1. (source: https://github.com/SpamScope/mail-parser/security/advisories/GHSA-r7w7-vpq8-c5vv)
- The address-header fallback runs when strict address parsing yields no usable address, e.g. a header like 'From: alice@example.com <bob@example.com>'. (source: https://github.com/SpamScope/mail-parser/security/advisories/GHSA-r7w7-vpq8-c5vv)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
Workaround: Cap total header size before parsing and enforce a wall-clock timeout around each parse. (source: https://github.com/SpamScope/mail-parser/security/advisories/GHSA-r7w7-vpq8-c5vv)
CISA KEV: CVE-2026-129295 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129295 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/SpamScope/mail-parser/security/advisories/GHSA-r7w7-vpq8-c5vv
- https://github.com/SpamScope/mail-parser/pull/166
- https://github.com/SpamScope/mail-parser/commit/037293158cb291caa96635a54449243d32cd4d96
- https://github.com/SpamScope/mail-parser/commit/5aab122f0d763991604d2c2bcc807c6bf2489464
- https://github.com/SpamScope/mail-parser/commit/85e53f820d78ae7c955dafbbcd0e20989a735c2c
- https://github.com/SpamScope/mail-parser/releases/tag/4.6.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129295
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129295"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- SpamScope mail-parser
From 4.2.0 · fixed in 4.6.1
Evidence 8
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Repository
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129295
Is CVE-2026-129295 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A few small crafted emails can make the parser's address-header fallback take a very long time, keeping mail parsing workers busy for minutes to hours of CPU time. The flaw is a denial of service with no confidentiality or integrity impact.Source: github.com
Which versions are affected by CVE-2026-129295?
mail-parser: from 4.2.0 before 4.6.1.Source: cve.now feed data
Am I affected, and how do I check?
Versions of mail-parser from 4.2.0 up to but not including 4.6.1 are affected. The fallback runs when strict address parsing yields no usable address, such as a From header like 'alice@example.com <bob@example.com>'. To check, look at the installed mail-parser version.Source: github.com
How do I fix CVE-2026-129295?
Upgrade mail-parser to 4.6.1 or later, which contains the fix. Until you can upgrade, cap total header size before parsing and enforce a wall-clock timeout around each parse.Source: github.com