Windows 10 1703 vulnerabilitiesAnd the versions its exploited flaws hit.

Product39 known exploited65 versions
The short answer

Windows 10 1703 is made by Microsoft. We track 47 published vulnerabilities in it, across 65 versions. 39 of them are on the list of flaws known to be exploited, the newest added on 3 March 2025. If you run Windows 10 1703, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Windows 10 1703 flaw added to the known-exploited list is CVE-2018-8639, on 3 March 2025. We keep watching the known-exploited list.

Versions

Which versions of Windows 10 1703 do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2019-0841Exploited list, 15 Mar 2022

    Microsoft Windows AppX Deployment Service (AppXSVC) Privilege Escalation Vulnerability

    all versions
  • CVE-2017-8464Exploited list, 10 Feb 2022

    Microsoft Windows Shell (.lnk) Remote Code Execution Vulnerability

    all versions

28 more exploited flaws name Windows 10 1703 without a version of its own, for example as the system other affected software runs on. They are in the list below.

Showing the 30 most recently added of 39 exploited flaws. The full list is below.

Known exploited

Which Windows 10 1703 vulnerabilities are being exploited?

39 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.8
    CVE-2018-8639HighKnown exploited
    Microsoft Windows Win32k Improper Resource Shutdown or Release Vulnerability

    Microsoft Windows Win32k contains an improper resource shutdown or release vulnerability that allows for local, authenticated privilege escalation.

    Chance of use22%Known exploited since3 Mar 2025
  2. 8.8
    CVE-2018-0824HighKnown exploited
    Microsoft COM for Windows Deserialization of Untrusted Data Vulnerability

    Microsoft COM for Windows contains a deserialization of untrusted data vulnerability that allows for privilege escalation and remote code execution via a specially crafted file or script.

    Chance of use73%Known exploited since5 Aug 2024
  3. 7.8
    CVE-2018-8611HighKnown exploited
    Microsoft Windows Kernel Privilege Escalation Vulnerability

    A privilege escalation vulnerability exists when the Windows kernel fails to properly handle objects in memory.

    Chance of use4.2%Known exploited since24 May 2022
  4. 9.8
    CVE-2017-8543CriticalKnown exploited
    Microsoft Windows Search Remote Code Execution Vulnerability

    Microsoft Windows allows an attacker to take control of the affected system when Windows Search fails to handle objects in memory.

    Chance of use74%Known exploited since24 May 2022
  5. 8.8
    CVE-2017-0210HighKnown exploited
    Microsoft Internet Explorer Privilege Escalation Vulnerability

    A privilege escalation vulnerability exists when Internet Explorer does not properly enforce cross-domain policies, which could allow an attacker to access information.

    Chance of use22%Known exploited since24 May 2022
  6. 6.5
    CVE-2019-0676MediumKnown exploited
    Microsoft Internet Explorer Information Disclosure Vulnerability

    An information disclosure vulnerability exists when Internet Explorer improperly handles objects in memory.

    Chance of use8.1%Known exploited since23 May 2022
  7. 7.8
    CVE-2019-1130HighKnown exploited
    Microsoft Windows AppX Deployment Service Privilege Escalation Vulnerability

    A privilege escalation vulnerability exists when Windows AppX Deployment Service (AppXSVC) improperly handles hard links.

    Chance of use1.7%Known exploited since23 May 2022
  8. 7.8
    CVE-2019-0880HighKnown exploited
    Microsoft Windows Privilege Escalation Vulnerability

    A local elevation of privilege vulnerability exists in how splwow64.exe handles certain calls.

    Chance of use2.3%Known exploited since23 May 2022
Exploit likelihood

Which Windows 10 1703 flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 90%
    CVE-2017-8464HighKnown exploited

    Windows Shell in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows...

    CVSS8.8Published15 Jun 2017
  2. 89%
    CVE-2017-8759HighKnown exploited

    Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to execute code remotely via a malicious document or application, aka ".NET Framework Remote Code Execution Vulnerability."

    CVSS7.8Published13 Sep 2017
  3. 88%
    CVE-2018-8174HighKnown exploited

    A remote code execution vulnerability exists in the way that the VBScript engine handles objects in memory, aka "Windows VBScript Engine Remote Code Execution Vulnerability." This affects Windows 7, Windows Server...

    CVSS7.5Published9 May 2018
  4. 84%
    CVE-2017-0213HighKnown exploited

    Windows COM Aggregate Marshaler in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server...

    CVSS7.3Published12 May 2017
  5. 74%
    CVE-2017-8543CriticalKnown exploited

    Microsoft Windows XP SP3, Windows XP x64 XP2, Windows Server 2003 SP2, Windows Vista, Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, Windows 8, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows...

    CVSS9.8Published15 Jun 2017
  6. 73%
    CVE-2018-0824HighKnown exploited

    A remote code execution vulnerability exists in "Microsoft COM for Windows" when it fails to properly handle serialized objects, aka "Microsoft COM for Windows Remote Code Execution Vulnerability." This affects...

    CVSS8.8Published9 May 2018
  7. 73%
    CVE-2018-8414HighKnown exploited

    A remote code execution vulnerability exists when the Windows Shell does not properly validate file paths, aka "Windows Shell Remote Code Execution Vulnerability." This affects Windows 10 Servers, Windows 10.

    CVSS8.8Published15 Aug 2018
  8. 70%
    CVE-2018-8453HighKnown exploited

    An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka "Win32k Elevation of Privilege Vulnerability." This affects Windows 7, Windows...

    CVSS7.8Published10 Oct 2018
Precursor Intelligence

Running Windows 10 1703? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 47 published vulnerabilities listed under the name Windows 10 1703, across 65 versions. The most recent Windows 10 1703 flaw added to the known-exploited list is CVE-2018-8639, on 3 March 2025.

39 are on the list of flaws known to be exploited. The most recently added are CVE-2018-8639, CVE-2018-0824 and CVE-2018-8611.

Each flaw names its own versions, usually as ranges. The newest, CVE-2019-0841, affects all versions. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Windows 10 1703. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.