CVE-2026-129307 · Package
NO FIX YET · SEE WHAT TO DO
eml_parser is a Python library that parses .eml email files. A crafted Received header causes a regular expression to backtrack exhaustively, pinning a parser worker and building a queue backlog.
first public Sep 7, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Services that parse email messages from untrusted senders with eml_parser through decode_email, decode_email_bytes or parse_email are exposed, since one unauthenticated message can stall a worker. Batch jobs that parse only mail you control can skip it.
Not affected if no-untrusted-email, offline-batch
Who cares email-parsing, eml_parser, python
pip show eml_parser to read the installed version; affected if it is 3.0.3 or earlierdecode_email, decode_email_bytes or parse_email run on untrusted incoming mail3.0.4eml_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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.