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

Published Nov 16, 2026
·
Updated

emlparser 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, emlparser.routing.parserouting() in emlparser/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 decodeemail, decodeemailbytes, and parseemail, so one small unauthenticated message can pin a parser worker and create sustained queue backlog. This issue is fixed in version 3.0.4.

Affected Software

1 affected component
pypi/eml_parser<=3.0.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.0.4

Event History

Nov 16, 2026
CVE Published
via MITRE·06:01 PM
Data Sourced
via MITRE·06:01 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this denial-of-service issue?

Applications that use eml_parser 3.0.3 or earlier to parse attacker-controlled email messages through decode_email, decode_email_bytes, or parse_email are exposed. A single small message with a crafted Received header can pin a parser worker and build a sustained processing backlog.

2

Does exploitation require authentication or user interaction?

No. The issue is reachable through an attacker-controlled Received header in an email message, and the supplied vector indicates network access with no privileges or user interaction required.

3

What should teams do if they cannot immediately upgrade?

The provided data identifies version 3.0.4 as the fix. Until upgrading, reduce exposure by preventing untrusted messages from reaching code paths that invoke decode_email, decode_email_bytes, or parse_email, or isolate parsing workers so a pinned worker cannot block the broader service.

4

How can I determine whether my deployment is affected?

Check the installed eml_parser version and whether your application processes untrusted EML content using decode_email, decode_email_bytes, or parse_email. Versions 3.0.3 and earlier are affected; version 3.0.4 contains the fix.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203