eml_parser vulnerable to DoS via deeply nested parens in Received headers
### Summary `eml_parser` strips parenthesised CFWS comments from `Received:` headers using a regex-based fix-point loop. The loop has quadratic time complexity in the number of nested parens. A single `Received:` header containing 5,000 nested parens causes ~1.3 seconds of CPU saturation per parsed message; runtime quadruples per doubling of nesting depth. ### Impact This represents a CPU exhaustion DoS in any pipeline that processes attacker-supplied EML files. An attacker can create relatively small EML files that will take multiple seconds to parse. This is particularly problematic for synchronous email-processing pipelines (gateways, sandboxes, real-time triage) where worker latency directly translates to queue backpressure and possible service-level outages. ### Patches Since version 3.0.2, `eml_parser` uses a linear-time algorithm to remove the comments from `Received:` headers.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-55620US | — | — | ||
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. Prior to 3.0.2, eml_parser.routing… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/GOVCERT-LU/eml_parserPACKAGE
- https://github.com/GOVCERT-LU/eml_parser/commit/746a69f86443eb0b6a47f77db3cfe727c21f92b3WEB
- https://github.com/GOVCERT-LU/eml_parser/pull/90WEB
- https://github.com/GOVCERT-LU/eml_parser/releases/tag/v3.0.2WEB
- https://github.com/GOVCERT-LU/eml_parser/security/advisories/GHSA-g7gc-gmgp-wgqgWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan