# CVE-2017-8543: Microsoft Windows Search Remote Code Execution

> An attacker can execute arbitrary code and take control of the system due to improper handling of objects in memory by Windows Search.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 24 May 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-w5g9-xvwm-4qf8

## What is CVE-2017-8543?

CVE-2017-8543 is a critical memory corruption vulnerability in Microsoft Windows 10 1507, published on 15 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allow an attacker to take control of the affected system when Windows Search fails to handle objects in memory, aka "Windows Search Remote Code Execution Vulnerability".

Weakness: CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2017-8543?

It affects 10 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1511, Microsoft Windows 10 1607, Microsoft Windows 10 1703, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016.

## How do I fix CVE-2017-8543?

No fix has been published for CVE-2017-8543 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Jun 2022.

## Is CVE-2017-8543 being exploited?

Yes. Attackers have exploited CVE-2017-8543 in the wild since at least 24 May 2022.

Public exploit code:

- InSpec profile to verify a node is patched and compliant for CVE-2017-8543 (github_poc): https://github.com/americanhanko/windows-security-cve-2017-8543

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)
- [CVE-2024-30040](https://insights.sbomify.com/CVE-2024-30040/): Microsoft Windows MSHTML Platform Security Feature Bypass (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8543 and fix it if it is affected.

What it is: CVE-2017-8543 is a critical memory corruption vulnerability in Microsoft Windows 10 1507, published on 15 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-8543 in the wild since at least 24 May 2022.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-8543/ (Markdown: https://insights.sbomify.com/CVE-2017-8543/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8543
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8543
- OSV: https://osv.dev/vulnerability/CVE-2017-8543

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-8543/
Summaries are generated and may contain mistakes; the official description above is the record.