dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-33827

HIGH · 8.1 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 →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows TCP/IP allows an unauthorized 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 race condition exists in the Windows TCP/IP stack where concurrent execution with improper synchronization on a shared resource allows an unauthenticated attacker to achieve remote code execution over the network. The vulnerability stems from improper handling of shared state during concurrent TCP/IP operations.

MitigationApply the relevant Microsoft Windows security update for this vulnerability once released; prioritize patching internet-facing systems and ensure regular patch management cycles include critical Windows TCP/IP stack updates.

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

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify Windows version and build number
    Open Command Prompt and run: winver OR run: systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
    Affected if Build number is below the fixed version for your Windows release (e.g., < 10.0.14393.9060 for Windows 10 1607, < 10.0.22631.6936 for Windows 11 23h2)
  2. Confirm TCP/IP stack is enabled
    Verify network adapter is present and TCP/IP protocol is bound: Open Network Connections, right-click adapter, select Properties, confirm 'Internet Protocol Version 4 (TCP/IPv4)' is checked
    Affected if TCP/IP is enabled and bound to a network adapter (default state for most Windows installations)
  3. Check if system is network-exposed
    Run: netsh interface show interface to list active network interfaces, then review firewall rules: netsh advfirewall firewall show rule name=all
    Affected if System has active network interfaces and allows inbound network connections (typical default Windows firewall configuration)
  4. Verify Windows Update history for TCP/IP patches
    Open Settings > Update & Security > Windows Update > View update history, or run: powershell "Get-HotFix | Where-Object {$_.Description -eq 'Security Update'} | Sort-Object InstalledOn -Descending | Select-Object -First 10"
    Affected if No security update matching this CVE (identified by KB number) is present in installed updates

Your system is affected if it runs any of the listed Windows versions with a build number lower than the fixed version AND has TCP/IP networking enabled and is network-accessible.

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 relevant Microsoft Windows security update for this vulnerability once released; prioritize patching internet-facing systems and ensure regular patch management cycles include critical Windows TCP/IP stack updates.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9060 | Windows 10 1809: build 10.0.17763.8644 | Windows 10 21h2: build 10.0.19044.7184 | Windows 10 22h2: build 10.0.19045.7184 | Windows 11 23h2: build 10.0.22631.6936 | Windows 11 24h2: build 10.0.26100.8246 | Windows 11 25h2: build 10.0.26200.8246 | Windows 11 26

  1. Open Windows Settings on the affected system
  2. Navigate to Windows Update (Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install the latest security updates
  4. After updates are installed, verify the OS build number matches or exceeds the fixed version for your Windows release
  5. Restart the system if prompted to complete the installation
Caveat Standard Windows security update with no expected breaking changes; as a remote code execution fix, applying this patch promptly is strongly recommended

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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