CVE-2018-3626

MEDIUMNVD 4.74.7—

4.7

Edger8r tool in the Intel SGX SDK before version 2.1.2 (Linux) and 1.9.6 (Windows) may generate code that is susceptible to a side channel potentially allowing a local user to access unauthorized information.

CVSS v3: 4.7
EG Score: 4.7(medium)
EPSS: 31.9%
KEV: Not listed

Published

March 20, 2018

Last Modified

November 21, 2024

References (4)

secure@intelhttp://www.securityfocus.com/bid/103479
secure@intelhttps://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00117&languageid=en-fr
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/103479
af854a3a-2127-422b-91ae-364da2661108https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00117&languageid=en-fr

Weakness Classification(1)

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

CWE-200Exposure of Sensitive Information to an Unauthorized Actor

Data Freshness Timeline

(refreshed 12× in last 7d / 20× 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-06 13:45 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-05 22:45 UTCepss_batch
2026-06-05 22:45 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 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:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 10:19 UTCEG score recompute
2026-05-28 10:19 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch

Frequently asked(5)

What is CVE-2018-3626?

CVE-2018-3626 is a medium vulnerability published on March 20, 2018. Edger8r tool in the Intel SGX SDK before version 2.1.2 (Linux) and 1.9.6 (Windows) may generate code that is susceptible to a side channel potentially allowing a local user to access unauthorized information.

When was CVE-2018-3626 disclosed?

CVE-2018-3626 was first published in the National Vulnerability Database on March 20, 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-3626 actively exploited?

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

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

CVE-2018-3626 has a CVSS v3 base score of 4.7 (NVD).

How do I remediate CVE-2018-3626?

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

Explore →

Is Your Infrastructure Affected by CVE-2018-3626?

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

Start Free Scan →Browse All CVEs

CVE-2018-3626

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-3626?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)