Skip to main content
VulnerabilityPublished

CVE-2026-129307: eml_parser · Algorithmic-complexity DoS (O(n^4) regex backtracking) in Received-header parsing

Affects eml-parserSource GCVE Database

0
Compare
Authoritative record:CVE-2026-129307· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.0.4 when convenient.

Data as of 19 Nov 2026, 23:23 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.3
Patch
Available – fixed in 3.0.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade eml-parser to 3.0.4.

Affected software

ProductAffectedFixed in
PyPIeml-parserAffected
  • <3.0.4
Fixed in
  • 3.0.4

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 eml-parser version 3.0.4 that resolves the algorithmic complexity vulnerability by removing the problematic static date suffix from the dynamic regex construction. Users should upgrade to version 3.0.4 or later to mitigate this issue. No other configuration or disabling options exist to avoid the vulnerable code path. Applying the official patch fully mitigates the risk.

Description

A regular expression denial of service (ReDoS) vulnerability exists in eml-parser versions prior to 3.0.4 in the Received-header parsing function. The vulnerability arises from a dynamically constructed regex with multiple greedy capture groups followed by a normalized date literal that may not match the original header line, causing catastrophic backtracking with O(n^4) complexity. This leads to high CPU usage and can hang parser workers on crafted email headers. The issue is fixed in version 3.0.4.

References

Community reviews

Loading reviews…