CVE-2026-55618

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.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, the clean_found_uri function in eml_parser/parser.py validates potential URL strings before unescaping HTML entities used for colon, slash, or period characters. Valid encoded URLs and their host names are therefore rejected and omitted from the extracted URL and domain lists. Email security gateways and SOC pipelines that use those lists as indicators of compromise may fail to submit the hidden URLs to threat intelligence feeds, reputation services, or sandboxes, allowing malicious links to bypass inspection. This issue is fixed in version 3.0.2.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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
githubMentions a patch (unverified)

URL extraction bypass via HTML entities in URLs · Advisory · GOVCERT-LU/eml_parser · GitHub

https://github.com/GOVCERT-LU/eml_parser/security/advisories/GHSA-fxgq-9m89-cxj9

Vendor Advisories for CVE-2026-55618(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(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 53× 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-10-10 20:00 UTCEPSS rescore
  2. 2026-10-10 11:45 UTCEG score recompute
  3. 2026-10-09 20:07 UTCEPSS rescore
  4. 2026-10-09 04:17 UTCEG score recompute
  5. 2026-10-08 17:12 UTCEPSS rescore
  6. 2026-10-08 02:54 UTCEG score recompute
  7. 2026-10-07 23:48 UTCEPSS rescore
  8. 2026-10-07 01:10 UTCEG score recompute
  9. 2026-10-06 15:18 UTCEPSS rescore
  10. 2026-10-06 02:29 UTCEG score recompute
  11. 2026-10-05 17:43 UTCEPSS rescore
  12. 2026-10-05 01:42 UTCEG score recompute
  13. 2026-10-04 23:22 UTCEPSS rescore
  14. 2026-10-04 03:21 UTCEG score recompute
  15. 2026-10-03 14:26 UTCEPSS rescore
  16. 2026-10-03 05:01 UTCEG score recompute
  17. 2026-10-02 17:56 UTCEPSS rescore
  18. 2026-10-02 06:27 UTCEG score recompute
  19. 2026-10-01 19:50 UTCEPSS rescore
  20. 2026-10-01 05:36 UTCEG score recompute
  21. 2026-09-30 15:03 UTCEPSS rescore
  22. 2026-09-30 06:42 UTCEG score recompute
  23. 2026-09-29 15:22 UTCEPSS rescore
  24. 2026-09-28 21:28 UTCEG score recompute
  25. 2026-09-28 13:51 UTCEPSS rescore
Show 56 more
  1. 2026-09-27 20:18 UTCEG score recompute
  2. 2026-09-27 13:48 UTCEPSS rescore
  3. 2026-09-26 21:59 UTCEG score recompute
  4. 2026-09-26 15:59 UTCEPSS rescore
  5. 2026-09-24 18:59 UTCEG score recompute
  6. 2026-09-24 14:04 UTCEPSS rescore
  7. 2026-09-23 20:40 UTCEG score recompute
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-22 22:22 UTCEG score recompute
  10. 2026-09-22 00:00 UTCEG score recompute
  11. 2026-09-21 01:41 UTCEG score recompute
  12. 2026-09-20 20:16 UTCEPSS rescore
  13. 2026-09-20 02:48 UTCEG score recompute
  14. 2026-09-19 04:28 UTCEG score recompute
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 06:10 UTCEG score recompute
  17. 2026-09-17 19:31 UTCEPSS rescore
  18. 2026-09-17 07:51 UTCEG score recompute
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 09:32 UTCEG score recompute
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-15 11:11 UTCEG score recompute
  23. 2026-09-15 03:11 UTCEPSS rescore
  24. 2026-09-14 12:46 UTCEG score recompute
  25. 2026-09-13 16:47 UTCEPSS rescore
  26. 2026-09-12 16:09 UTCEG score recompute
  27. 2026-09-11 17:51 UTCEG score recompute
  28. 2026-09-11 14:53 UTCEPSS rescore
  29. 2026-09-10 19:32 UTCEG score recompute
  30. 2026-09-10 09:35 UTCEPSS rescore
  31. 2026-09-09 04:46 UTCEG score recompute
  32. 2026-09-08 22:01 UTCEPSS rescore
  33. 2026-09-07 08:05 UTCEG score recompute
  34. 2026-09-06 13:47 UTCEPSS rescore
  35. 2026-09-06 09:16 UTCEG score recompute
  36. 2026-09-05 10:49 UTCEG score recompute
  37. 2026-09-04 12:31 UTCEG score recompute
  38. 2026-09-04 05:06 UTCEPSS rescore
  39. 2026-09-02 15:44 UTCEG score recompute
  40. 2026-09-02 14:12 UTCEPSS rescore
  41. 2026-09-01 17:07 UTCEG score recompute
  42. 2026-09-01 13:54 UTCEPSS rescore
  43. 2026-09-01 04:40 UTCEPSS rescore
  44. 2026-08-30 20:05 UTCEG score recompute
  45. 2026-08-30 19:17 UTCEPSS rescore
  46. 2026-08-30 01:22 UTCEPSS rescore
  47. 2026-08-28 23:28 UTCEG score recompute
  48. 2026-08-28 22:51 UTCEG score recompute
  49. 2026-08-28 21:41 UTCEPSS rescore
  50. 2026-08-27 16:06 UTCEG score recompute
  51. 2026-08-27 14:25 UTCEPSS rescore
  52. 2026-08-26 17:46 UTCEG score recompute
  53. 2026-08-26 14:46 UTCEPSS rescore
  54. 2026-08-25 19:20 UTCEG score recompute
  55. 2026-08-25 18:30 UTCEG score recompute
  56. 2026-08-25 18:29 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55618?
CVE-2026-55618 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, the cleanfounduri function in emlparser/parser.py validates potential URL strings before unescaping HTML entities used for colon, slash,…
When was CVE-2026-55618 disclosed?
CVE-2026-55618 was first published 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-55618 actively exploited?
CVE-2026-55618 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55618?
CVE-2026-55618 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55618?
A fix for CVE-2026-55618 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55618 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-55618

Explore →

Is Your Infrastructure Affected by CVE-2026-55618?

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

Book a Demo →Browse All CVEs