CVE-2026-55620

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.noparenthesis in eml_parser/routing.py removes parenthesized CFWS comments from Received: headers with a regex-based fix-point loop whose running time is quadratic in the nesting depth. A single Received: header with 5,000 nested parentheses causes approximately 1.3 seconds of CPU saturation per parsed message, and doubling the nesting depth approximately quadruples the running time. An attacker can submit relatively small EML files that consume multiple seconds of processing time, causing worker latency, queue backpressure, and possible service-level outages in synchronous gateways, sandboxes, and real-time triage pipelines. This issue is fixed in version 3.0.2.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

v3.0.2

Patch available: GOVCERT-LU/eml_parser v3.0.2

https://github.com/GOVCERT-LU/eml_parser/releases/tag/v3.0.2
GitHub commit Patch Available

commit 746a69f86443 (GOVCERT-LU/eml_parser)

Patch available: GOVCERT-LU/eml_parser v3.0.2 (contains commit 746a69f86443)

https://github.com/GOVCERT-LU/eml_parser/commit/746a69f86443eb0b6a47f77db3cfe727c21f92b3
GitHub pull request Patch Available

Address security advisories

Patch available: GOVCERT-LU/eml_parser v3.0.2 (PR #90 merged 2026-06-15)

https://github.com/GOVCERT-LU/eml_parser/pull/90
GitHub advisoryMentions a patch (unverified)

DoS via deeply nested parens in Received headers · Advisory · GOVCERT-LU/eml_parser · GitHub

https://github.com/GOVCERT-LU/eml_parser/security/advisories/GHSA-g7gc-gmgp-wgqg

Vendor Advisories for CVE-2026-55620(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
eml-parser0.9 ... 3.0.1 (41 versions)
  • every version up to 3.0.2: fixed in 3.0.2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 56× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:17 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-10 11:44 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-09 04:09 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-08 02:53 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-07 01:10 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-10-06 02:28 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-10-05 01:42 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-10-03 16:21 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-10-02 18:04 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-10-01 20:01 UTCEG score recompute
Show 68 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-09-30 20:14 UTCEG score recompute
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  4. 2026-09-30 06:42 UTCEG score recompute
  5. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-09-29 08:29 UTCEG score recompute
  7. 2026-09-28 21:28 UTCEG score recompute
  8. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-09-27 20:07 UTCEG score recompute
  10. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-09-26 21:59 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-09-24 18:51 UTCEG score recompute
  14. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-09-23 20:35 UTCEG score recompute
  16. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-09-22 22:33 UTCEG score recompute
  18. 2026-09-22 00:29 UTCEG score recompute
  19. 2026-09-21 02:26 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-19 17:15 UTCEG score recompute
  22. 2026-09-19 06:14 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-09-17 21:08 UTCEG score recompute
  25. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  26. 2026-09-16 21:34 UTCEG score recompute
  27. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  28. 2026-09-16 09:23 UTCEG score recompute
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-09-15 09:40 UTCEG score recompute
  31. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  32. 2026-09-14 00:37 UTCEG score recompute
  33. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-09-12 15:34 UTCEG score recompute
  35. 2026-09-11 17:31 UTCEG score recompute
  36. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  37. 2026-09-10 19:16 UTCEG score recompute
  38. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  39. 2026-09-09 01:11 UTCEG score recompute
  40. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  41. 2026-09-07 17:58 UTCEG score recompute
  42. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  43. 2026-09-06 19:53 UTCEG score recompute
  44. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  45. 2026-09-05 21:47 UTCEG score recompute
  46. 2026-09-04 23:41 UTCEG score recompute
  47. 2026-09-04 11:53 UTCEG score recompute
  48. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  49. 2026-09-02 15:44 UTCEG score recompute
  50. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-09-01 17:07 UTCEG score recompute
  52. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  53. 2026-09-01 05:51 UTCEG score recompute
  54. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  55. 2026-08-30 20:27 UTCEG score recompute
  56. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  57. 2026-08-30 09:26 UTCEG score recompute
  58. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  59. 2026-08-29 00:15 UTCEG score recompute
  60. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  61. 2026-08-27 14:45 UTCEG score recompute
  62. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  63. 2026-08-26 16:43 UTCEG score recompute
  64. 2026-08-26 15:58 UTCEG score recompute
  65. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  66. 2026-08-25 19:20 UTCEG score recompute
  67. 2026-08-25 18:30 UTCEG score recomputeFirst assessed: 7.5 HIGH
  68. 2026-08-25 18:29 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55620?
CVE-2026-55620 is a high-severity vulnerability; its CVE record was published on August 25, 2026. emlparser 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, emlparser.routing.noparenthesis in eml_parser/routing.py removes parenthesized CFWS comments from Received: headers with a regex-based…
When was the CVE record for CVE-2026-55620 published?
The CVE record for CVE-2026-55620 was published on August 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55620 actively exploited?
CVE-2026-55620 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55620?
CVE-2026-55620 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55620?
A fix for CVE-2026-55620 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55620 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55620

Explore →

Is Your Infrastructure Affected by CVE-2026-55620?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs