dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-23669

HIGH · 8.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Use after free in RPC Runtime allows an authorized attacker to execute code over a network.

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 use-after-free vulnerability in the RPC Runtime allows an authenticated attacker to achieve remote code execution by leveraging memory that is freed but still referenced, causing memory corruption when the dangling pointer is dereferenced.

MitigationApply the vendor-provided patch for the RPC Runtime component; if unavailable, audit and fix memory allocation/deallocation patterns to ensure pointers are nullified immediately after freeing.

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.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719

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

CVSS:3.1/AV:N/AC:L/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 build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full Windows build number
    Affected if The build number falls below the safe thresholds: 14393.8957 (1607), 17763.8511 (1809), 19044.7058 (21h2), 19045.7058 (22h2), 22631.6783 (23h2), 26100.7979 (24h2), 26200.7979 (25h2), or 28000.1719 (26h1)
  2. Verify RPC Runtime component is present
    Check for the presence of rpcrt4.dll in System32 (typically at C:\Windows\System32\rpcrt4.dll) using File Explorer or 'dir C:\Windows\System32\rpcrt4.dll'
    Affected if The rpcrt4.dll file exists and its version is older than expected for the installed Windows build
  3. Confirm RPC services are enabled
    Run 'Get-Service -Name RpcSs, DcomLaunch, RpcEptMapper' in PowerShell to check if core RPC services are running
    Affected if Any of these critical RPC services are running (which is the default state on Windows) and the Windows version is below the fixed builds
  4. Check for authenticated user context
    Review system logs and user session information using 'query user' or Security Event Log entries to determine if authenticated sessions exist
    Affected if Authenticated users or service accounts are actively using the system, as the attacker requires valid credentials to exploit this flaw

You are affected if your Windows build number is lower than the safe threshold for your specific Windows version and the RPC Runtime component is active on the system.

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.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply the vendor-provided patch for the RPC Runtime component; if unavailable, audit and fix memory allocation/deallocation patterns to ensure pointers are nullified immediately after freeing.

Recommended fix High confidence

Windows 10 1607 to 10.0.14393.8957 or later | Windows 10 1809 to 10.0.17763.8511 or later | Windows 10 21h2 to 10.0.19044.7058 or later | Windows 10 22h2 to 10.0.19045.7058 or later | Windows 11 23h2 to 10.0.22631.6783 or later | Windows 11 24h2 to 10.0.26100.7979 or later | Windows 11 25h2 to 10.0.

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest cumulative update
  3. Ensure the installed version meets or exceeds the minimum fixed version for your Windows release: Windows 10 1607 requires 10.0.14393.8957, Windows 10 1809 requires 10.0.17763.8511, Windows 10 21h2 requires 10.0.19044.7058, Windows 10 22h2 requires 10.0.19045.7058, Windows 11 23h2 requires 10.0.22631.6783, Windows 11 24h2 requires 10.0.26100.7979, Windows 11 25h2 requires 10.0.26200.7979, and Wind
  4. Restart the system after the update is installed
  5. Verify the installed version by running 'winver' or 'systeminfo' to confirm the update was applied successfully
Caveat Standard Windows update with minimal risk; ensure standard backup practices are followed before applying updates in production environments

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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