CVE-2018-6218

HIGHNVD 7.07.0—Trending — 3 sources updated this week

7.0

A DLL Hijacking vulnerability in Trend Micro's User-Mode Hooking Module (UMH) could allow an attacker to run arbitrary code on a vulnerable system.

CVSS v3: 7.0
EG Score: 7.0(medium)
EPSS: 58.3%
KEV: Not listed

Published

February 16, 2018

Last Modified

November 21, 2024

References (8)

security@trendmicrohttp://www.securityfocus.com/bid/103096
security@trendmicrohttps://jvn.jp/jp/JVN28865183/
security@trendmicrohttps://success.trendmicro.com/jp/solution/1119348
security@trendmicrohttps://success.trendmicro.com/solution/1119326
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/103096
af854a3a-2127-422b-91ae-364da2661108https://jvn.jp/jp/JVN28865183/
af854a3a-2127-422b-91ae-364da2661108https://success.trendmicro.com/jp/solution/1119348
af854a3a-2127-422b-91ae-364da2661108https://success.trendmicro.com/solution/1119326

Weakness Classification(1)

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

CWE-426Untrusted Search Path

Data Freshness Timeline

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

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 11:17 UTCEG score recompute
2026-05-28 11:17 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-23 03:05 UTCOSV refresh

Frequently asked(5)

What is CVE-2018-6218?

CVE-2018-6218 is a high vulnerability published on February 16, 2018. A DLL Hijacking vulnerability in Trend Micro's User-Mode Hooking Module (UMH) could allow an attacker to run arbitrary code on a vulnerable system.

When was CVE-2018-6218 disclosed?

CVE-2018-6218 was first published in the National Vulnerability Database on February 16, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-6218 actively exploited?

CVE-2018-6218 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 58.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-6218?

CVE-2018-6218 has a CVSS v3 base score of 7.0 (NVD).

How do I remediate CVE-2018-6218?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6218, 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-2018-6218

Explore →

Is Your Infrastructure Affected by CVE-2018-6218?

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

Start Free Scan →Browse All CVEs

CVE-2018-6218

📅 Published

🔄 Last Modified

🔗 References (8)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-6218?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (8)

Frequently asked(5)

Related CVEs(same CWE)