Skip to main content
Menu
CVEs

CVE

eml_parser denial of service in Received-header parsing

CVE-2026-129307EUVD-2026-126577

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.0.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.0.4.

Published
Last modified
Reference
Last checked
22/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The eml_parser Python module from GOVCERT-LU mishandles Received headers in e-mail messages, causing it to consume excessive processing time. A remote attacker can send one small message, without logging in or any user action, to tie up a parser worker and create a sustained processing backlog, which is a denial of service.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original 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.

cve.now Index

22Pcve.now Index 22 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.0.4.

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-129307 (eml_parser: Algorithmic-complexity DoS (O(n^4) regex backtracking) in Received-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-129307 (entry last updated 2026-11-16):
Affected:
- GOVCERT-LU eml_parser: fixed in 3.0.4
Fixed versions: 3.0.4.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129307 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129307 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/GOVCERT-LU/eml_parser/security/advisories/GHSA-m4g8-47f9-h588
- https://github.com/GOVCERT-LU/eml_parser/commit/54ea6e9f54fecda3059283ccdb6a6fd99e7ce92f
- https://github.com/GOVCERT-LU/eml_parser/releases/tag/v3.0.4
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-129307
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-129307"}.

Timeline

  1. CVE published
  2. Record last updated
  3. First seen by cve.now

Affected versions

  • GOVCERT-LU eml_parser

    fixed in 3.0.4

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Repository
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129307

Is CVE-2026-129307 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

Which versions are affected by CVE-2026-129307?

eml_parser: before 3.0.4.Source: cve.now feed data

How do I fix CVE-2026-129307?

Upgrade to a fixed version: 3.0.4.Source: cve.now feed data