dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26232

HIGH · 7.3 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.10240.20596 / 10.0.14393.6897 or later.
See remediation →
73/100
Remediation priority · Elevated

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
Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability

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 is a Remote Code Execution vulnerability in Microsoft Message Queuing (MSMQ), a Windows component for asynchronous message communication. An attacker could exploit this vulnerability remotely to execute arbitrary code on affected systems without explicit details on the attack vector or authentication requirements.

MitigationApply available Microsoft security updates for CVE-2024-26232. If patching is not immediately feasible, disable MSMQ or restrict network access to MSMQ ports (1801, 2101, 2103, 2105, 2107) at perimeter firewalls.

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 1507Operating system
Affected:< 10.0.10240.20596
Windows 10 1607Operating system
Affected:< 10.0.14393.6897
Windows 10 1809Operating system
Affected:< 10.0.17763.5696
Windows 10 21h2Operating system
Affected:< 10.0.19044.4291
Windows 10 22h2Operating system
Affected:< 10.0.19045.4291
Windows 11 21h2Operating system
Affected:< 10.0.22000.2899
Windows 11 22h2Operating system
Affected:< 10.0.22621.3447
Windows 11 23h2Operating system
Affected:< 10.0.22631.3447

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Confirm MSMQ is installed
    Run Get-WindowsOptionalFeature -Online -FeatureName MSMQ in PowerShell to see if the Message Queuing feature is enabled, or check for the presence of the msmq service via Get-Service msmq
    Affected if The MSMQ feature is installed or the msmq service exists on the system
  2. Verify MSMQ service status
    Run Get-Service msmq to check if the Microsoft Message Queuing service is running
    Affected if The msmq service status is Running
  3. Check Windows version
    Run winver or run "systeminfo | findstr /B /C:"OS Name" /C:"OS Version"" to identify the exact Windows version and build number
    Affected if The installed Windows version and build number fall below the fixed versions: Windows 10 1507 < 10.0.10240.20596, 1607 < 10.0.14393.6897, 1809 < 10.0.17763.5696, 21h2 < 10.0.19044.4291, 22h2 < 10.0.19045.4291; Windows 11 21h2 < 10.0.22000.2899, 22h2 < 10.0.22621.3447, 23h2 < 10.0.22631.3447
  4. Identify MSMQ listening ports
    Run netstat -ano | findstr "1801" to check if MSMQ ports are open and listening
    Affected if Ports 1801, 2101, 2103, 2105, or 2107 are in a LISTENING state indicating MSMQ is exposed on the network

The system is affected if it runs a vulnerable Windows version from the affected list AND has MSMQ installed with the service running or exposed on the network.

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.10240.20596 / 10.0.14393.6897 / 10.0.17763.5696 or later
Fixed in 10.0.10240.2059610.0.14393.689710.0.17763.5696
Interim mitigation

Apply available Microsoft security updates for CVE-2024-26232. If patching is not immediately feasible, disable MSMQ or restrict network access to MSMQ ports (1801, 2101, 2103, 2105, 2107) at perimeter firewalls.

Recommended fix High confidence

Windows 10/11 with security updates meeting minimum build versions (10.0.10240.20596 for 1507, 10.0.14393.6897 for 1607, 10.0.17763.5696 for 1809, 10.0.19044.4291 for 21h2, 10.0.19045.4291 for 22h2, 10.0.22000.2899 for Win11 21h2, 10.0.22621.3447 for Win11 22h2, 10.0.22631.3447 for Win11 23h2)

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Update by going to Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Ensure the installed build number meets or exceeds the fixed version for your Windows edition: Windows 10 1507 requires 10.0.10240.20596 or later; Windows 10 1607 requires 10.0.14393.6897 or later; Windows 10 1809 requires 10.0.17763.5696 or later; Windows 10 21h2 requires 10.0.19044.4291 or later; Windows 10 22h2 requires 10.0.19045.4291 or later; Windows 11 21h2 requires 10.0.22000.2899 or later
  5. Restart the computer to complete the security update installation
  6. Verify the update was successfully applied by checking the installed Windows version again
Caveat Standard Windows security update with minimal risk; may require restart

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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