dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-32085

MEDIUM · 5.5 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 →
57/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
Exposure of sensitive information to an unauthorized actor in Windows Remote Procedure Call allows an authorized attacker to disclose information 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 · high confidence

This is a local information disclosure vulnerability in Windows Remote Procedure Call (RPC). An authorized attacker with local access can exploit Windows RPC to disclose sensitive information that they should not have access to. The vulnerability requires the attacker to have some form of valid credentials or authorization on the target system, but does not require administrator privileges.

MitigationApply the Microsoft security update for CVE-2026-32085 via Windows Update or your organization's patch management process. Verify that RPC services are running with least-privilege service accounts and follow principle of least privilege for user accounts.

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to see the full build number
    Affected if The build number is lower than any of these: 14393.9060 (Win10 1607), 17763.8644 (Win10 1809), 19044.7184 (Win10 21h2/22h2), 22631.6936 (Win11 23h2), 26100.8246 (Win11 24h2/25h2), or 28000.1836 (Win11 26h1)
  2. Verify RPC service status
    Open Services console (services.msc) or run 'sc query rpcss' in Command Prompt to check if the Remote Procedure Call (RPC) service is running
    Affected if The RPC service is running (this is the default state; the vulnerability applies when RPC is active)
  3. Confirm security update is absent
    Run 'wmic qfe list' or check Windows Update history in Settings > Windows Update > Update history for a security update corresponding to CVE-2026-32085
    Affected if No security update for CVE-2026-32085 is listed in the installed updates

You are affected if your Windows build version is lower than the fixed builds listed AND the RPC service is running AND the CVE-2026-32085 security update 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.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 the Microsoft security update for CVE-2026-32085 via Windows Update or your organization's patch management process. Verify that RPC services are running with least-privilege service accounts and follow principle of least privilege for user accounts.

Recommended fix High confidence

Install the Windows security update containing the fix for CVE-2026-32085 (specific KB number available at msrc.microsoft.com) - version requirements: Windows 10 1607: 10.0.14393.9060 | Windows 10 1809: 10.0.17763.8644 | Windows 10 21h2: 10.0.19044.7184 | Windows 10 22h2: 10.0.19045.7184 | Windows 1

  1. Open Windows Settings on the affected system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, manually download the specific security update from the Microsoft Update Catalog matching your Windows version (KB reference available at msrc.microsoft.com)
  5. Restart the system after the update is installed
  6. Verify the installed update by checking Windows Update history
Caveat Standard Windows security update - minimal risk; patch is cumulative and includes other security fixes

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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