CVE-2026-50384
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 Windows Clip Service allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 Clip Service where concurrent access to shared resources lacks proper synchronization. An authorized local attacker can exploit this timing vulnerability to manipulate the service's behavior and elevate privileges to a higher integrity level, potentially achieving SYSTEM privileges.
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.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525< 10.0.17763.9020< 10.0.20348.5386CVSS 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.
-
Check Windows version and build numberOpen Command Prompt or PowerShell and run `winver` or `Get-ComputerInfo | Select-Object OsVersion, OsBuildNumber` to retrieve the exact Windows version and build numberAffected if The build number is lower than the fixed version for your Windows release (17763.9020 for Windows 10 1809/Server 2019, 19044.7548 for Windows 10 21h2, 19045.7548 for Windows 10 22h2, 26100.8875 for Windows 11 24h2, 26200.8875 for Windows 11 25h2, 28000.2525 or 28000.2269 for Windows 11 26h1, 20348.5
-
Identify Windows release versionRun `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to determine if you are running Windows 10, Windows 11, or Windows Server and which specific release (such as 1809, 21h2, 22h2, 24h2, 25h2, or 26h1)Affected if The OS is identified as one of the affected versions listed in the CVE and the build number falls below the corresponding threshold
-
Verify Clip Service presence and statusRun `Get-Service cbdhsvc*` in PowerShell to check if the Clipboard Service (cbdhsvc) or related clipboard access services are installed and running on the systemAffected if The Clipboard Service (cbdhsvc) is present and running, as the vulnerability exists within this service component
You are affected if your Windows version and build number match any of the affected ranges listed and the Clipboard Service is actively 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.17763.902010.0.19044.754810.0.19045.7548
Apply the official Microsoft security patch for this vulnerability once released; until then, restrict local access to trusted users only and monitor for suspicious processes interacting with the Clip Service.
Windows 10 1809/Server 2019: 10.0.17763.9020+ | Windows 10 21h2: 10.0.19044.7548+ | Windows 10 22h2: 10.0.19045.7548+ | Windows 11 24h2: 10.0.26100.8875+ | Windows 11 25h2: 10.0.26200.8875+ | Windows 11 26h1: 10.0.28000.2525+ | Windows Server 2022: 10.0.20348.5386+
- 1. Identify the current Windows build version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
- 2. Determine if the current build is vulnerable by comparing against the fixed builds: Windows 10 1809/Server 2019 need 10.0.17763.9020 or later, Windows 10 21h2 needs 10.0.19044.7548 or later, Windows 10 22h2 needs 10.0.19045.7548 or later, Windows 11 24h2 needs 10.0.26100.8875 or later, Windows 11 25h2 needs 10.0.26200.8875 or later, Windows 11 26h1 needs 10.0.28000.2525 or later (or 10.0.28000.
- 3. Apply the applicable Microsoft security update for this vulnerability from the Microsoft Security Response Center (msrc.microsoft.com)
- 4. Restart the system as prompted by the update installation
- 5. Verify the fix by checking the installed build matches or exceeds the fixed build number for your Windows version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50384 — 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-50384 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