CVE-2026-32093
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 · uneditedConcurrent execution using shared resource with improper synchronization ('race condition') 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 confidenceA race condition vulnerability exists in the Windows Function Discovery Service (fdwsd.dll) where improper synchronization of shared resources allows an authorized local attacker to manipulate timing and elevate privileges to higher permission levels.
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< 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< 10.0.28000.1836CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' or 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v BuildLabEx'Affected if The displayed build number is lower than any of the affected version thresholds (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)
-
Check Function Discovery service statusRun 'sc query FDResPub' or 'Get-Service -Name FDResPub' in PowerShellAffected if The service state shows as RUNNING (the vulnerability requires the service to be active)
You are affected if your Windows build number is below the thresholds AND the Function Discovery service (FDResPub) is running on your system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.906010.0.17763.864410.0.19044.7184
Apply vendor-provided security patches for Windows systems once available; minimize local attack surface by restricting user permissions and monitoring for suspicious process activity.
Windows 10/11 with build numbers >= the fixed version for each respective release (as listed above), or migrate to the latest supported Windows 11 version
- Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
- Determine which Windows 10 or 11 version is installed and check if the build number is below the fixed version for that release
- For Windows 10 1607: Upgrade to build 10.0.14393.9060 or later
- For Windows 10 1809: Upgrade to build 10.0.17763.8644 or later
- For Windows 10 21h2: Upgrade to build 10.0.19044.7184 or later
- For Windows 10 22h2: Upgrade to build 10.0.19045.7184 or later
- For Windows 11 23h2: Upgrade to build 10.0.22631.6936 or later
- For Windows 11 24h2: Upgrade to build 10.0.26100.8246 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32093 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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