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.
CVE-2026-55618
MEDIUMPre-NVD 6.56.5
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 6.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(low)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (4)
Auto-updated Aug 25, 2026Patch 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.2github_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/746a69f86443eb0b6a47f77db3cfe727c21f92b3github_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/90github Patch Available
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-cxj9Vendor Advisories for CVE-2026-55618(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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.
- 2026-08-25 19:20 UTCEG score recompute
- 2026-08-25 18:30 UTCEG score recompute
- 2026-08-25 18:29 UTCMITRE cvelistV5first tracked
Frequently asked(4)
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 in the National Vulnerability Database on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-55618?
CVE-2026-55618 has a CVSS v3 base score of 6.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-55618?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55618, 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
Explore the affected products and dependency analysis for CVE-2026-55618
Is Your Infrastructure Affected by CVE-2026-55618?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.