An information disclosure vulnerability exists when Microsoft Excel improperly discloses the contents of its memory, aka "Microsoft Excel I…

published 2018-05-09 8y ago modified 2026-06-17 4mo ago also EUVD-2018-19834

cvss: 5.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 12.9%; EPSS 12.9% chance of exploitation in 30 days, percentile 96%
public exploits: 0; none known

An information disclosure vulnerability exists when Microsoft Excel improperly discloses the contents of its memory, aka "Microsoft Excel Information Disclosure Vulnerability." This affects Microsoft Office, Microsoft Excel.

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8163 advisory

Is CVE-2018-8163 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

12.92% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.5	CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2018-8163
patch, vendor-advisory
securitytracker.com /id/1040857
vdb-entry, third-party-advisory
securityfocus.com /bid/104059
vdb-entry, third-party-advisory

Sources

CVE List CVE-2018-8163
NVD CVE-2018-8163

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.