dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32087

HIGH · 7.0 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.14393.9060 / 10.0.17763.8644 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Heap-based buffer overflow in Function Discovery Service (fdwsd.dll) allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A heap-based buffer overflow vulnerability exists in the Function Discovery Service (fdwsd.dll) on Windows systems. An authorized attacker can exploit this memory corruption flaw to gain elevated privileges locally, potentially achieving SYSTEM-level access on the affected machine.

MitigationApply vendor-provided security updates for the Function Discovery Service. If no patch is available, consider disabling the Function Discovery Service if not required, or implement least-privilege policies to limit authorized users' capabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the exact Windows build. Alternatively, check the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuildNumber.
    Affected if The installed version falls within any of the affected version ranges (less than 10.0.14393.9060, 10.0.17763.8644, 10.0.19044.7184, 10.0.19045.7184, 10.0.22631.6936, 10.0.26100.8246, 10.0.26200.8246, or 10.0.28000.1836).
  2. Verify Function Discovery Service status
    Run 'Get-Service -Name fdWSearch' in PowerShell, or 'sc query fdWSearch' in Command Prompt.
    Affected if The service is in a Running state, as the vulnerability requires the Function Discovery Service to be active for exploitation.
  3. Locate and verify fdwsd.dll version
    Find the file at C:\Windows\System32\fdwsd.dll (or use 'Get-ChildItem -Path C:\Windows\System32 -Filter fdwsd.dll'). Right-click the file, select Properties, and check the Details tab for the File Version.
    Affected if The DLL file version is present on the system and matches a version associated with the affected Windows builds.

You are affected if your Windows build falls within the vulnerable version ranges AND the Function Discovery Service (fdWSearch) is currently running on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.9060 / 10.0.17763.8644 / 10.0.19044.7184 or later
Fixed in 10.0.14393.906010.0.17763.864410.0.19044.7184
Interim mitigation

Apply vendor-provided security updates for the Function Discovery Service. If no patch is available, consider disabling the Function Discovery Service if not required, or implement least-privilege policies to limit authorized users' capabilities.

Recommended fix High confidence

Windows security update to the specific fixed build number for each affected version (10.0.14393.9060, 10.0.17763.8644, 10.0.19044.7184, 10.0.19045.7184, 10.0.22631.6936, 10.0.26100.8246, 10.0.26200.8246, or 10.0.28000.1836 depending on Windows version)

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which affected version category applies (Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 23h2, 24h2, 25h2, 26h1)
  3. Apply the appropriate Windows security update for the specific build version from Microsoft Update Catalog or WSUS
  4. For Windows 10 1607: update to build 10.0.14393.9060 or later
  5. For Windows 10 1809: update to build 10.0.17763.8644 or later
  6. For Windows 10 21h2: update to build 10.0.19044.7184 or later
  7. For Windows 10 22h2: update to build 10.0.19045.7184 or later
  8. For Windows 11 23h2: update to build 10.0.22631.6936 or later
Caveat Standard Windows security update; minimal risk of breaking changes; apply per normal patch management process

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32087 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data