dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50372

HIGH · 7.0 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
72/100
Remediation priority · Elevated
Zero-click 5 weeks old

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
Buffer over-read in Windows Redirected Drive Buffering allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

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 confidence

A buffer over-read vulnerability exists in Windows Redirected Drive Buffering, a component of Remote Desktop Services that manages drive mappings between client and server. The flaw allows an authorized attacker to read beyond buffer boundaries, leading to local privilege elevation from their current authenticated state.

MitigationApply Microsoft security updates for Windows that address the Redirected Drive Buffering vulnerability. Monitor Microsoft's monthly security advisory for the relevant patch.

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.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269< 10.0.28000.2525
Windows Server 2012Operating system
Affected:all versions= r2

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
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to retrieve the exact Windows version and build number.
    Affected if The installed version falls within any of these vulnerable ranges: Windows 10 1607 < 10.0.14393.9339, Windows 10 1809 < 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.
  2. Verify Remote Desktop Services status
    Open Services (services.msc) and check if 'Remote Desktop Services' or 'Remote Desktop Services (TermService)' is running, or run 'Get-Service TermService' in PowerShell.
    Affected if Remote Desktop Services is enabled and running on an affected Windows version.
  3. Confirm Redirected Drive Buffering is in use
    Check if drive redirection is enabled by opening Remote Desktop Connection (mstsc), clicking 'Show Options', going to the 'Local Resources' tab, and verifying if 'Drives' is checked under 'Local devices and resources'. Alternatively, check registry key 'HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters' for related entries.
    Affected if Drive redirection is configured or actively used on a system with Remote Desktop Services enabled.
  4. Check for presence of security patch
    Run 'wmic qfe list' or 'Get-HotFix | Sort-Object InstalledOn' in PowerShell to list installed updates. Look for the Microsoft security update corresponding to this CVE in the installed patches list.
    Affected if The specific security update for this CVE is NOT installed and the Windows version matches an affected vulnerable range.
  5. Review Windows Event Logs for RDS drive access anomalies
    Open Event Viewer and navigate to 'Windows Logs' > 'Security' or 'Applications and Services Logs' > 'Microsoft' > 'Windows' > 'TerminalServices' for suspicious drive mapping events or abnormal read operations.
    Affected if Unusual or excessive drive read events are logged in TerminalServices logs on an unpatched system with RDS enabled.

You are affected if your Windows version matches any of the listed vulnerable builds AND Remote Desktop Services with drive redirection is enabled, and the corresponding security patch is not installed.

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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply Microsoft security updates for Windows that address the Redirected Drive Buffering vulnerability. Monitor Microsoft's monthly security advisory for the relevant patch.

Recommended fix High confidence

Windows 10 1607 -> 10.0.14393.9339 or later | Windows 10 1809 -> 10.0.17763.9020 or later | Windows 10 21h2 -> 10.0.19044.7548 or later | Windows 10 22h2 -> 10.0.19045.7548 or later | Windows 11 24h2 -> 10.0.26100.8875 or later | Windows 11 25h2 -> 10.0.26200.8875 or later | Windows 11 26h1 -> 10.0.

  1. Check current Windows version and build number by running 'winver' or 'systeminfo' in command prompt
  2. For Windows 10 (1607, 1809, 21h2, 22h2) and Windows 11 (24h2, 25h2, 26h1): Apply the latest Windows Security Update from Windows Update or Microsoft Update Catalog
  3. Verify the installed version matches or exceeds the fixed build: 10.0.14393.9339 (1607), 10.0.17763.9020 (1809), 10.0.19044.7548 (21h2), 10.0.19045.7548 (22h2), 10.0.26100.8875 (24h2), 10.0.26200.8875 (25h2), or 10.0.28000.2525 (26h1)
  4. For Windows Server 2012/R2: This version is end-of-life with no patch available; migrate to a supported Windows Server version (2016, 2019, 2022, or 2025)
Caveat Upgrading Windows 10 to newer builds may require re-configuration of enterprise policies; Windows Server 2012/R2 migration requires application compatibility testing and potential hardware assessment for newer server versions

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50372 — 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-50372 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