dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-26254

HIGH · 7.5 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.17763.5696 / 10.0.19044.4291 or later.
See remediation →
84/100
Remediation priority · High
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
Microsoft Virtual Machine Bus (VMBus) Denial of Service 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

A denial of service vulnerability exists in Microsoft Virtual Machine Bus (VMBus), a kernel-mode component that handles communication between parent and child partitions in Hyper-V environments. An unauthenticated attacker could exploit this to cause a DoS condition, potentially affecting virtual machine availability and host stability.

MitigationApply Microsoft security updates for affected Windows versions running Hyper-V or the Hyper-V role. Test virtualization workloads post-patch to ensure VM availability and host communication are unaffected.

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 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
Windows Server 2019Operating system
Affected:< 10.0.17763.5696
Windows Server 2022Operating system
Affected:< 10.0.20348.2402

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 Hyper-V role is installed
    Run 'Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V' in PowerShell or check Server Manager for the Hyper-V role. Alternatively, check if the VMBus service exists with 'Get-Service vmicheartbeat' or verify hypervisor launcher is present.
    Affected if Hyper-V is NOT installed - the VMBus component is not present and this CVE does not apply. The vulnerability only affects systems with the Hyper-V role enabled.
  2. Identify installed Windows version and build number
    Run 'winver' from Run dialog or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt. Alternatively, run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShell.
    Affected if The system is not one of the listed affected Windows versions (Windows 10 1809+, Windows 11 21h2+, Windows Server 2019+, or Windows Server 2022).
  3. Compare build number against CVE thresholds
    Run 'winver' or 'systeminfo' to obtain the exact build number (for example, 10.0.19045.4291). Compare your build to the affected threshold for your specific Windows version from the CVE: Windows 10 1809/Server 2019: < 10.0.17763.5696; Windows 10 21h2: < 10.0.19044.4291; Windows 10 22h2: < 10.0.19045.4291; Windows 11 21h2: < 10.0.22000.2899; Windows 11 22h2: < 10.0.22621.3447; Windows 11 23h2: < 10.0.22631.3447; Windows Server 2022: < 10.0.20348.2402.
    Affected if Your installed build number falls BELOW the threshold for your specific Windows version and Hyper-V is installed.

You are affected if Hyper-V is enabled and your Windows build number is lower than the version threshold listed for your specific Windows release.

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.17763.5696 / 10.0.19044.4291 / 10.0.19045.4291 or later
Fixed in 10.0.17763.569610.0.19044.429110.0.19045.4291
Interim mitigation

Apply Microsoft security updates for affected Windows versions running Hyper-V or the Hyper-V role. Test virtualization workloads post-patch to ensure VM availability and host communication are unaffected.

Recommended fix High confidence

Windows 10 1809: build 10.0.17763.5696 | Windows 10 21h2: build 10.0.19044.4291 | Windows 10 22h2: build 10.0.19045.4291 | Windows 11 21h2: build 10.0.22000.2899 | Windows 11 22h2: build 10.0.22621.3447 | Windows 11 23h2: build 10.0.22631.3447 | Windows Server 2019: build 10.0.17763.5696 | Windows S

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which product line and version you are running (Windows 10 1809, 21h2, 22h2, Windows 11 21h2, 22h2, 23h2, Windows Server 2019, or Windows Server 2022)
  3. Apply the appropriate Windows Security Update that addresses CVE-2024-26254
  4. For Windows 10 1809: Upgrade to build 10.0.17763.5696 or later
  5. For Windows 10 21h2: Upgrade to build 10.0.19044.4291 or later
  6. For Windows 10 22h2: Upgrade to build 10.0.19045.4291 or later
  7. For Windows 11 21h2: Upgrade to build 10.0.22000.2899 or later
  8. For Windows 11 22h2: Upgrade to build 10.0.22621.3447 or later
Caveat Standard Windows cumulative update; no breaking changes expected for most environments

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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