CVE-2026-129307

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

Published Nov 16, 2026 CVSS 3.1 · 5.3 Medium EPSS n/a KEV · Not listed
Description
eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. In 3.0.3 and earlier, eml_parser.routing.parserouting() in eml_parser/routing.py builds a regular expression with multiple greedy capture groups and appends the npdate date literal extracted from a normalized copy of an attacker-controlled Received header, then searches that expression against the original unnormalized line. A formatting difference can make the trailing literal impossible to match, causing exhaustive backtracking across the greedy groups at each start position. The unsliced Received-header path is invoked by decode_email, decode_email_bytes, and parse_email, so one small unauthenticated message can pin a parser worker and create sustained queue backlog. This issue is fixed in version 3.0.4.

Analysis

AI-generated

Technical impact

eml_parser uses a regular expression with multiple greedy capture groups to parse the Received header in the routing module. When an attacker supplies a Received header that includes a date literal which does not match the unnormalized original line, the regex triggers exhaustive backtracking at every start position, causing a time complexity of O(n^4). This workload can stall the parser worker and build a sustained backlog of queued emails, effectively denying service to legitimate traffic. The weakness aligns with CWE-1333 (Backtracking Attack) and CWE-407 (Time‑based Attack).

Affected Systems

The vulnerability is present in all releases of the GOVCERT‑LU:eml_parser package up to and including version 3.0.3. The fix was released in version 3.0.4 and removes the problematic regex construction. No other vendors or product versions are listed as affected.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. No EPSS score is available, so the likelihood of exploitation is unknown. The vulnerability is not listed in CISA KEV. Attackers can trigger the flaw by sending a crafted email containing a malicious Received header to any application that uses eml_parser for parsing. No authentication is required, so a remote or local attacker with the ability to submit email can exploit the flaw. The primary attack vector is message ingestion via the parsing code.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade eml_parser to version 3.0.4 or later to eliminate the vulnerable regex construction.
  • If an upgrade cannot be performed immediately, modify the application to sanitize or strip the Received header before it is passed to eml_parser.routing.parserouting(), ensuring that no unnormalized header is used for regex matching.
  • Configure email reception policies to reject or truncate overly long Received headers, and monitor the parser service for high CPU usage or queue backlogs to detect attempted exploitation.

Generated by OpenCVE AI on November 16, 2026 at 20:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Govcert-lu
Govcert-lu eml Parser
Vendors & Products Govcert-lu
Govcert-lu eml Parser
Type Values Removed Values Added
Description eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. In 3.0.3 and earlier, eml_parser.routing.parserouting() in eml_parser/routing.py builds a regular expression with multiple greedy capture groups and appends the npdate date literal extracted from a normalized copy of an attacker-controlled Received header, then searches that expression against the original unnormalized line. A formatting difference can make the trailing literal impossible to match, causing exhaustive backtracking across the greedy groups at each start position. The unsliced Received-header path is invoked by decode_email, decode_email_bytes, and parse_email, so one small unauthenticated message can pin a parser worker and create sustained queue backlog. This issue is fixed in version 3.0.4.
Title eml_parser: Algorithmic-complexity DoS (O(n^4) regex backtracking) in Received-header parsing
Weaknesses CWE-1333
CWE-407
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-1333

    Inefficient Regular Expression Complexity

  • CWE-407

    Inefficient Algorithmic Complexity

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 6:03 PM
Reserved
Nov 13, 2026, 10:30 PM
Status
Deferred
Published
Nov 16, 2026, 7:17 PM
Modified
Nov 16, 2026, 7:17 PM