dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-49076

HIGH · 7.8 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.17763.6659 / 10.0.19044.5247 or later.
See remediation →
80/100
Remediation priority · High
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
Windows Virtualization-Based Security (VBS) Enclave Elevation of Privilege 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 local Elevation of Privilege vulnerability in Windows Virtualization-Based Security (VBS) Enclave. An attacker with low-level privileges can exploit this to gain higher privileges by bypassing VBS Enclave security boundaries. The 7.8 CVSS score indicates low attack complexity, no user interaction required, and high impact on confidentiality, integrity, and availability.

MitigationApply the Microsoft security update for CVE-2024-49076 to all affected Windows systems. Prioritize systems where VBS is enabled, as these are directly impacted. Verify VBS functionality remains intact after patching.

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.6659
Windows 10 21h2Operating system
Affected:< 10.0.19044.5247
Windows 10 22h2Operating system
Affected:< 10.0.19045.5247
Windows 11 22h2Operating system
Affected:< 10.0.22621.4602
Windows 11 23h2Operating system
Affected:< 10.0.22631.4602
Windows 11 24h2Operating system
Affected:< 10.0.26100.2605
Windows Server 2019Operating system
Affected:< 10.0.17763.6659
Windows Server 2022Operating system
Affected:< 10.0.20348.2966

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

CVSS:3.1/AV:L/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 "Build"' or check the registry value at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuild. Compare your build number against the affected ranges: 17763.6659, 19044.5247, 19045.5247, 22621.4602, 22631.4602, 26100.2605, and 20348.2966 depending on your Windows version.
    Affected if Your Windows build number is lower than the threshold for your specific Windows version and build.
  2. Confirm VBS is enabled
    Run 'msinfo32' and look for 'Virtualization-Based Security' status, or run 'Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard' in PowerShell to check VirtualizationBasedSecurityStatus.
    Affected if VBS is shown as 'Running' or enabled in the output. The vulnerability only affects systems where VBS is actively running.
  3. Check VBS Enclave configuration
    Run 'ls C:\Windows\System32\enclave\' to list enclave binaries, or check if the Hyper-V Enclave feature is installed via 'Get-WindowsOptionalFeature -Online -FeatureName *Enclave*'.
    Affected if VBS Enclave or Hyper-V Enclave features are present and enabled on the system.

You are affected if your Windows build is below the threshold for your version AND VBS (Virtualization-Based Security) is currently running on your 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.17763.6659 / 10.0.19044.5247 / 10.0.19045.5247 or later
Fixed in 10.0.17763.665910.0.19044.524710.0.19045.5247
Interim mitigation

Apply the Microsoft security update for CVE-2024-49076 to all affected Windows systems. Prioritize systems where VBS is enabled, as these are directly impacted. Verify VBS functionality remains intact after patching.

Recommended fix High confidence

Windows 10 1809 to build 17763.6659+, Windows 10 21H2 to build 19044.5247+, Windows 10 22H2 to build 19045.5247+, Windows 11 22H2 to build 22621.4602+, Windows 11 23H2 to build 22631.4602+, Windows 11 24H2 to build 26100.2605+, Windows Server 2019 to build 17763.6659+, Windows Server 2022 to build 2

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which affected version range your system falls into based on the output
  3. Apply the appropriate Windows update or cumulative update that includes the fix for CVE-2024-49076
  4. For Windows 10 1809 systems: Upgrade to build 10.0.17763.6659 or later
  5. For Windows 10 21H2 systems: Upgrade to build 10.0.19044.5247 or later
  6. For Windows 10 22H2 systems: Upgrade to build 10.0.19045.5247 or later
  7. For Windows 11 22H2 systems: Upgrade to build 10.0.22621.4602 or later
  8. For Windows 11 23H2 systems: Upgrade to build 10.0.22631.4602 or later
Caveat Standard Windows update risks apply - ensure backups and test in staging environment before production deployment

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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