How severe is CVE-2017-8718?

CVE-2017-8718 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2017-8718 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 23% (97th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-8718?

CVE-2017-8718 primarily affects Microsoft Windows 10. In total, 12 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-8718?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-8718 published?

CVE-2017-8718 was published on 2017-10-13 and last updated on 2026-06-17.

CVE-2017-8718

CVE-2017-8718 is a high-severity vulnerability in Microsoft Windows 10 with a CVSS 3.x base score of 7.8. Its EPSS exploit-prediction score of 23% places it in the 97th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-119.

Key facts

Severity: High (CVSS 3.x base score 7.8)
CVSS v2: 9.3
EPSS exploit prediction: 23% (97th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-119
Affected product: Microsoft Windows 10
Published: 2017-10-13
Last modified: 2026-06-17

Description

The Microsoft JET Database Engine in Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1 and RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows an attacker to take control of an affected system, due to how it handles objects in memory, aka "Microsoft JET Database Engine Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8717.

Frequently asked questions

What is CVE-2017-8718?: The Microsoft JET Database Engine in Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1 and RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows an attacker to take control of an affected system, due to how it handles objects in memory, aka "Microsoft JET Database Engine Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8717.
How severe is CVE-2017-8718?: CVE-2017-8718 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-8718 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 23% (97th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-8718?: CVE-2017-8718 primarily affects Microsoft Windows 10. In total, 12 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-8718?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-8718 published?: CVE-2017-8718 was published on 2017-10-13 and last updated on 2026-06-17.

References

Affected products (12)

cpe:2.3:o:microsoft:windows_10:-:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1511:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1607:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10:1703:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_7:*:sp1:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_8.1:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_rt_8.1:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2008:*:sp2:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2012:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:*:*:*:*

More vulnerabilities in Microsoft Windows 10

CVE-2020-1467 — Critical (CVSS 10.0): An elevation of privilege vulnerability exists when Windows improperly handles hard links. An attacker who successfully…
CVE-2021-26424 — Critical (CVSS 9.9): Windows TCP/IP Remote Code Execution Vulnerability
CVE-2021-28476 — Critical (CVSS 9.9): Windows Hyper-V Remote Code Execution Vulnerability
CVE-2021-26867 — Critical (CVSS 9.9): Windows Hyper-V Remote Code Execution Vulnerability
CVE-2020-1112 — Critical (CVSS 9.9): An elevation of privilege vulnerability exists when the Windows Background Intelligent Transfer Service (BITS) IIS…
CVE-2019-1384 — Critical (CVSS 9.9): A security feature bypass vulnerability exists where a NETLOGON message is able to obtain the session key and sign…

All CVEs affecting Microsoft Windows 10 →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

CVE-2026-2778 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the DOM: Core & HTML component. This vulnerability was fixed in…
CVE-2026-2776 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the Telemetry component in External Software. This vulnerability…
CVE-2025-1866 — Critical (CVSS 10.0): Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in warmcat libwebsockets allows…
CVE-2022-27625 — Critical (CVSS 10.0): A vulnerability regarding improper restriction of operations within the bounds of a memory buffer is found in the…
CVE-2022-27624 — Critical (CVSS 10.0): A vulnerability regarding improper restriction of operations within the bounds of a memory buffer is found in the…
CVE-2020-11896 — Critical (CVSS 10.0): The Treck TCP/IP stack before 6.0.1.66 allows Remote Code Execution, related to IPv4 tunneling.

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →