dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-34329

HIGH · 8.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 or later.
See remediation →
93/100
Remediation priority · Urgent
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
Heap-based buffer overflow in Windows Message Queuing allows an unauthorized attacker to execute code over an adjacent 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 · high confidence

Heap-based buffer overflow vulnerability in Windows Message Queuing (MSMQ) service allows an unauthenticated attacker on an adjacent network to achieve remote code execution by sending specially crafted malicious messages to the MSMQ service.

MitigationApply Microsoft security updates for Windows when released. If MSMQ is not required in the environment, disable or uninstall the feature. Restrict network access to MSMQ listening ports from untrusted network segments as an interim measure.

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.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/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. Verify if MSMQ feature is installed
    Open PowerShell and run: Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like '*MSMQ*'} | Select-Object FeatureName, State
    Affected if MSMQ is installed and enabled (State equals 'Enabled')
  2. Check Windows 10 build version
    Run 'winver' or 'systeminfo' from command prompt, or in PowerShell: [System.Environment]::OSVersion.Version.Build
    Affected if Build number is less than 14393.9140 (1607), 17763.8755 (1809), 19044.7291 (21h2), or 19045.7291 (22h2)
  3. Check Windows 11 build version
    Run 'winver' or in PowerShell: [System.Environment]::OSVersion.Version.Build
    Affected if Build number is less than 22631.7079 (23h2), 26100.8390 (24h2), 26200.8390 (25h2), or 28000.2113 (26h1)
  4. Verify MSMQ service is running
    In PowerShell run: Get-Service -Name MSMQ | Select-Object Name, Status
    Affected if Service status is 'Running'
  5. Confirm MSMQ is listening on network ports
    In PowerShell run: Get-NetTCPConnection -State Listen | Where-Object {$_.LocalPort -in @(1801, 3525, 2101, 2103, 2105)}
    Affected if MSMQ is listening on any of the standard MSMQ ports (1801, 3525, 2101, 2103, 2105) and is network-accessible

System is affected if MSMQ is installed and enabled AND the Windows build version falls below the threshold for the corresponding Windows release, and MSMQ 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.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply Microsoft security updates for Windows when released. If MSMQ is not required in the environment, disable or uninstall the feature. Restrict network access to MSMQ listening ports from untrusted network segments as an interim measure.

Recommended fix High confidence

Apply the Microsoft security update for CVE-2026-34329 which brings Windows to the fixed build versions (10.0.14393.9140, 10.0.17763.8755, 10.0.19044.7291, 10.0.19045.7291, 10.0.22631.7079, 10.0.26100.8390, 10.0.26200.8390, or 10.0.28000.2113 depending on Windows version)

  1. 1. Open Windows Settings on the affected system
  2. 2. Navigate to Windows Update (Settings > Update & Security > Windows Update)
  3. 3. Click 'Check for updates' to fetch the latest security patches
  4. 4. Install all available updates, specifically looking for the security update that addresses CVE-2026-34329 in Windows Message Queuing
  5. 5. Restart the system if prompted to complete the installation
  6. 6. Verify the installed Windows version matches or exceeds the fixed build number for your Windows version (1607: 10.0.14393.9140, 1809: 10.0.17763.8755, 21h2: 10.0.19044.7291, 22h2: 10.0.19045.7291, 23h2: 10.0.22631.7079, 24h2: 10.0.26100.8390, 25h2: 10.0.26200.8390, 26h1: 10.0.28000.2113)
  7. 7. Alternatively, use Windows Server Update Services (WSUS), Microsoft Update Catalog, or enterprise deployment tools to deploy the monthly security update containing the CVE-2026-34329 fix
Caveat Standard Windows update risks apply - review Microsoft KB article for the specific update for any known issues before deploying in production

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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