dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50365

HIGH · 8.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 →
83/100
Remediation priority · High
No privileges 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
Improper authentication in Windows RPC API allows an unauthorized attacker to elevate privileges over an adjacent network.

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

This vulnerability in Windows RPC API involves improper authentication handling that permits an unauthenticated attacker on an adjacent network to escalate privileges. The flaw allows a network-based attacker to bypass authentication checks in the RPC interface and gain elevated access to the affected Windows system.

MitigationApply Microsoft security updates for Windows when available. In the interim, restrict RPC exposure through network segmentation, firewall rules, and disable RPC over TCP/IP if not required. Monitor for anomalous RPC traffic on adjacent network segments.

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number
    Affected if The installed version matches one of the affected products and the build number is lower than the specified threshold (e.g., Windows 10 22h2 with build < 10.0.19045.7548)
  2. Identify Windows edition
    Run 'winver' or check System Properties to confirm whether the system is Windows Server 2012 or Windows Server 2012 R2 specifically
    Affected if The system is Windows Server 2012 or Windows Server 2012 R2 (all versions are affected)
  3. Verify RPC over TCP/IP status
    Check registry key HKLM\SYSTEM\CurrentControlSet\Services\RpcSs for 'Start' value (2 = auto-enabled) and review if DCOM/RPC endpoints are configured. Use 'netsh rpc show all' to list RPC endpoints bound to network interfaces
    Affected if RPC over TCP/IP is enabled and bound to network interfaces accessible from adjacent networks
  4. Assess network exposure of RPC ports
    Run 'netstat -an | findstr "135 445 49152-49188"' to identify listening RPC-related ports, and verify firewall rules with 'netsh advfirewall firewall show rule name=all' to confirm whether inbound RPC traffic is permitted
    Affected if RPC ports (135, 445, dynamic ports) are listening on accessible network interfaces and firewall rules allow inbound RPC connections from adjacent network segments

A system is affected if it runs a vulnerable Windows version (or Windows Server 2012/R2) AND has RPC over TCP/IP enabled and exposed to adjacent networks, allowing unauthenticated attackers to bypass authentication checks.

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.

From vendor data
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 when available. In the interim, restrict RPC exposure through network segmentation, firewall rules, and disable RPC over TCP/IP if not required. Monitor for anomalous RPC traffic on adjacent network segments.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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