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

> A tiny crafted email with a malicious Received header triggers catastrophic regex backtracking, pinning workers and exhausting queue space in apps using eml_parser.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** AZL-114286, GHSA-m4g8-47f9-h588

## What is CVE-2026-129307?

CVE-2026-129307 is a medium-severity denial of service vulnerability in GOVCERT-LU eml_parser, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-407 (Inefficient Algorithmic Complexity), CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-129307?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-129307?

No fix has been published for CVE-2026-129307 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129307 being exploited?

There is no known exploitation of CVE-2026-129307 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129307 and fix it if it is affected.

What it is: CVE-2026-129307 is a medium-severity denial of service vulnerability in GOVCERT-LU eml_parser, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129307 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: GOVCERT-LU eml_parser. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129307/ (Markdown: https://insights.sbomify.com/CVE-2026-129307/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129307
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129307
- OSV: https://osv.dev/vulnerability/CVE-2026-129307

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129307/
Summaries are generated and may contain mistakes; the official description above is the record.
