CVE-2026-55620: CWE-770: Allocation of Resources Without Limits or Throttling in GOVCERT-LU eml_parser
Description
CVE-2026-55620 is a high-severity vulnerability in the GOVCERT-LU eml_parser Python module prior to version 3.0.2. The flaw involves a regex-based fix-point loop in the function eml_parser.routing.noparenthesis that removes parenthesized comments from Received: headers. This loop has quadratic time complexity relative to the nesting depth of parentheses, causing excessive CPU consumption when processing emails with deeply nested parentheses. An attacker can exploit this by submitting crafted EML files with deeply nested parentheses, leading to significant processing delays and potential denial of service in synchronous email processing systems. The issue is fixed in version 3.0.2. No official patch advisory or exploit reports are currently available.
CVSS v3.1
Score 7.5high
Affected software
GOVCERT-LU
eml_parser
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The eml_parser Python module used for parsing EML files contains a resource exhaustion vulnerability (CWE-770) due to a regex-based fix-point loop in eml_parser.routing.noparenthesis that removes parenthesized CFWS comments from Received: headers. This loop's runtime grows quadratically with the nesting depth of parentheses. For example, a Received: header with 5,000 nested parentheses causes about 1.3 seconds of CPU saturation per message, and doubling the nesting depth quadruples processing time. This can be exploited by attackers submitting small but computationally expensive EML files, causing worker latency, queue backpressure, and potential service outages in real-time email processing pipelines. The vulnerability is fixed in eml_parser version 3.0.2.
Potential Impact
The vulnerability leads to denial of service conditions by consuming excessive CPU resources during email parsing. This can cause increased latency, queue backpressure, and possible outages in synchronous gateways, sandboxes, and real-time triage pipelines that rely on eml_parser. There is no impact on confidentiality or integrity reported. No known exploits are currently in the wild.
Mitigation Recommendations
Upgrade eml_parser to version 3.0.2 or later, where this issue is fixed. No other mitigation or temporary workaround is documented. Patch status is not explicitly confirmed by a vendor advisory, but the fix is stated to be in version 3.0.2.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T23:31:22.446Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a8de143acd9273b4991a18f
Added to database: 08/25/2026, 18:38:59 UTC
Last enriched: 09/10/2026, 02:07:13 UTC
Last updated: 10/08/2026, 06:48:18 UTC
Views: 49
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.