dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26177

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 10.0.10240.20526 / 10.0.14393.6796 or later.
See remediation →
57/100
Remediation priority · Elevated
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 Kernel Information Disclosure 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 Windows Kernel information disclosure vulnerability that allows an attacker to read sensitive information from kernel memory. The CVSS 5.5 score indicates it is exploitable but requires some user interaction or specific conditions. The vulnerability could expose sensitive data such as memory addresses or other kernel-mode information that could aid in further exploitation.

MitigationApply the Microsoft security update addressing CVE-2024-26177 through Windows Update or by deploying the relevant patch through your organization's patch management system.

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.20526
Windows 10 1607Operating system
Affected:< 10.0.14393.6796
Windows 11 23h2Operating system
Affected:< 10.0.22631.3296
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.6796
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.763

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 version and build number
    Run 'winver' or check System Properties, or run 'systeminfo' in command prompt to display the OS version and build number
    Affected if The displayed version and build number fall within any of the affected ranges listed below
  2. Identify if running Windows 10 1507
    Verify if the OS shows version 1507 (initial release) and note the build number shown in winver or systeminfo
    Affected if Build number is less than 10.0.10240.20526
  3. Identify if running Windows 10 1607
    Verify if the OS shows version 1607 (Anniversary Update) and note the build number
    Affected if Build number is less than 10.0.14393.6796
  4. Identify if running Windows 11 23H2
    Verify if the OS shows version 23H2 and note the build number
    Affected if Build number is less than 10.0.22631.3296
  5. Identify if running Windows Server 2016
    Check if the system is Windows Server 2016 and note the build number
    Affected if Build number is less than 10.0.14393.6796
  6. Identify if running Windows Server 2022 23H2
    Check if the system is Windows Server 2022 23H2 and note the build number
    Affected if Build number is less than 10.0.25398.763

If the installed Windows version and build number match any of the affected ranges listed (including all versions of Windows Server 2008 R2 and Windows Server 2012 R2), the system is affected by this vulnerability.

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.20526 / 10.0.14393.6796 / 10.0.22631.3296 or later
Fixed in 10.0.10240.2052610.0.14393.679610.0.22631.3296
Interim mitigation

Apply the Microsoft security update addressing CVE-2024-26177 through Windows Update or by deploying the relevant patch through your organization's patch management system.

Recommended fix High confidence

Upgrade to the fixed builds: Windows 10 1607/Server 2016 to build 10.0.14393.6796; Windows 11 23H2/Server 2022 23H2 to build 10.0.22631.3296/10.0.25398.763 respectively; migrate unsupported systems (Server 2008, 2012, Win10 1507) to supported releases

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows 10 1607 and Windows Server 2016: Upgrade to Windows build 10.0.14393.6796 or later via Windows Update, or download and install the cumulative update from the Microsoft Update Catalog
  3. For Windows 11 23H2: Upgrade to Windows build 10.0.22631.3296 or later via Windows Update
  4. For Windows Server 2022 23H2: Upgrade to Windows build 10.0.25398.763 or later via Windows Update
  5. For Windows 10 1507 (build < 10.0.10240.20526): Microsoft no longer supports this version; migrate to a supported Windows 10 or 11 release
  6. For Windows Server 2008/2012 (all versions): Microsoft no longer supports these versions; migrate to a supported Windows Server version (2016, 2019, 2022, or 2025)
  7. After upgrade, verify the kernel version matches or exceeds the fixed build using 'systeminfo' command
Caveat Older systems (Server 2008, Server 2012, Windows 10 1507) are end-of-life with no patches available; must migrate to newer Windows versions which may require application compatibility testing

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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