dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-49126

HIGH · 8.1 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.10240.20857 / 10.0.14393.7606 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
Windows Local Security Authority Subsystem Service (LSASS) 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 the Windows Local Security Authority Subsystem Service (LSASS), a critical Windows process that handles authentication, security policy enforcement, and user logon operations. Successful exploitation could allow an attacker to execute arbitrary code in the context of the LSASS process, potentially achieving privilege escalation and full system compromise.

MitigationApply Microsoft security updates for CVE-2024-49126 immediately. Prioritize patching domain controllers and systems with sensitive credentials, as LSASS handles authentication for the entire domain.

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.20857
Windows 10 1607Operating system
Affected:< 10.0.14393.7606
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

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. Check Windows build number
    Run 'winver' from command prompt or check the Build number in System Properties. Alternatively, run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
    Affected if The displayed build number is lower than the threshold for your Windows release (see step 2)
  2. Identify Windows release version
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and note both the CurrentBuild and DisplayVersion values to determine your specific Windows 10 or 11 release (e.g., 1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, or 24h2)
    Affected if You cannot determine your exact Windows release version from the build number alone
  3. Compare against affected version ranges
    Cross-reference your identified Windows release and build number against: Windows 10 1507 < 10.0.10240.20857, Windows 10 1607 < 10.0.14393.7606, Windows 10 1809 < 10.0.17763.6659, Windows 10 21h2 < 10.0.19044.5247, Windows 10 22h2 < 10.0.19045.5247, Windows 11 22h2 < 10.0.22621.4602, Windows 11 23h2 < 10.0.22631.4602, Windows 11 24h2 < 10.0.26100.2605
    Affected if Your installed build number falls below the fixed version for your specific Windows release

You are affected if your Windows version and build number are lower than the threshold listed for your specific Windows release (10 1507, 10 1607, 10 1809, 10 21h2, 10 22h2, 11 22h2, 11 23h2, or 11 24h2).

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.20857 / 10.0.14393.7606 / 10.0.17763.6659 or later
Fixed in 10.0.10240.2085710.0.14393.760610.0.17763.6659
Interim mitigation

Apply Microsoft security updates for CVE-2024-49126 immediately. Prioritize patching domain controllers and systems with sensitive credentials, as LSASS handles authentication for the entire domain.

Recommended fix High confidence

Apply the appropriate Windows Security Update for your Windows version that includes the CVE-2024-49126 fix

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which security update addresses CVE-2024-49126 from the Microsoft Security Update Guide (msrc.microsoft.com)
  3. Apply the relevant Windows security update for your version via Windows Update, or download from Microsoft Update Catalog
  4. Restart the system to complete the update installation
  5. Verify the LSASS version matches the fixed build number for your Windows version (e.g., 10.0.10240.20857 for 1507, 10.0.14393.7606 for 1607, etc.)
Caveat Standard Windows security update - may require restart; ensure compatibility with critical line-of-business applications before deployment

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

Fix this in Windows 10 1507 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-2024-49126 — 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-49126 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