CVE-2026-55619

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.parser.HeaderParser.header_fetch_parse in eml_parser/parser.py uses email.utils.getaddresses() to parse address-bearing e-mail headers. A deeply nested CFWS comment construct exhausts the standard-library recursive descent parser's call stack and raises RecursionError, which is not caught and therefore aborts parsing of the entire message. An attacker can disrupt SOC pipelines that process untrusted EML files, although callers already need to handle exceptions from malformed or pathological messages. This issue is fixed in version 3.0.2.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
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_pr 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 Patch Available

Parser DoS via deeply nested parentheses in e-mail headers · Advisory · GOVCERT-LU/eml_parser · GitHub

https://github.com/GOVCERT-LU/eml_parser/security/advisories/GHSA-m66c-fw79-6359

Vendor Advisories for CVE-2026-55619(1)

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 rangeFixed inDependents
eml-parser0.9 ... 3.0.1 (41 versions)3.0.2—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 12:04 UTCEG score recompute
  3. 2026-09-17 19:31 UTCEPSS rescore
  4. 2026-09-16 14:14 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 14:48 UTCEG score recompute
  8. 2026-09-15 03:11 UTCEPSS rescore
  9. 2026-09-13 17:00 UTCEG score recompute
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-12 18:06 UTCEG score recompute
  12. 2026-09-11 19:12 UTCEG score recompute
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 20:08 UTCEG score recompute
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-09 04:46 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 05:42 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-07 06:35 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-06 07:32 UTCEG score recompute
  23. 2026-09-05 08:39 UTCEG score recompute
  24. 2026-09-04 09:45 UTCEG score recompute
  25. 2026-09-04 05:06 UTCEPSS rescore
Show 20 more
  1. 2026-09-03 10:52 UTCEG score recompute
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-02 11:55 UTCEG score recompute
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 12:55 UTCEG score recompute
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-31 14:01 UTCEG score recompute
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 14:58 UTCEG score recompute
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-29 16:04 UTCEG score recompute
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-27 18:11 UTCEG score recompute
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 19:17 UTCEG score recompute
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 20:23 UTCEG score recompute
  18. 2026-08-25 19:20 UTCEG score recompute
  19. 2026-08-25 18:30 UTCEG score recompute
  20. 2026-08-25 18:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55619?
CVE-2026-55619 is a medium vulnerability 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.parser.HeaderParser.headerfetchparse in eml_parser/parser.py uses email.utils.getaddresses() to parse address-bearing e-mail…
When was CVE-2026-55619 disclosed?
CVE-2026-55619 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55619 actively exploited?
CVE-2026-55619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.9% of all scored CVEs.
What is the CVSS score of CVE-2026-55619?
CVE-2026-55619 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-55619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55619, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55619?

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

Start Free Scan →Browse All CVEs