dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26229

HIGH · 7.8 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 →
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 CSC Service 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 the Windows Client-Side Caching (CSC) service (also known as Offline Files). An authenticated local attacker could exploit improper privilege handling in the CSC service to execute code with elevated SYSTEM-level privileges, bypassing standard user account controls.

MitigationApply the Microsoft security update KB5002537 (April 2024) or subsequent relevant patches for CVE-2024-26229. If the CSC service is not required in the environment, it can be disabled as a defense-in-depth measure.

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
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 version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' and compare the build number to the vulnerable version thresholds: 10.0.10240.20596 (1507), 10.0.14393.6897 (1607), 10.0.17763.5696 (1809), 10.0.19044.4291 (21h2), 10.0.19045.4291 (22h2), 10.0.22000.2899 (Win11 21h2), 10.0.22621.3447 (Win11 22h2), 10.0.22631.3447 (Win11 23h2).
    Affected if The installed Windows build number is lower than the corresponding threshold for your Windows version.
  2. Verify if CSC/Offline Files service is enabled
    Open Services (services.msc), locate 'Client-Side Caching (CSC)', or run 'Get-Service -Name CscService' in PowerShell. Check if the service status is Running or set to Automatic.
    Affected if The CSC service exists and is enabled (Running or set to start automatically).
  3. Check for installed security update
    Run 'Get-HotFix | Where-Object {$_.HotFixID -eq "KB5002537"}' in PowerShell, or open Control Panel > Programs > View installed updates and search for KB5002537 or later date-based updates from April 2024 onward.
    Affected if KB5002537 or a subsequent relevant security patch is NOT installed.
  4. Confirm service executable exists
    Verify the CSC service binary exists at '%SystemRoot%\System32\cscsvc.dll' or '%SystemRoot%\System32\csc.exe' if the service is present.
    Affected if The CSC service binaries are present on the system.

You are affected if your Windows build is below the threshold for your version AND the CSC service is enabled AND the security update KB5002537 is not installed.

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 the Microsoft security update KB5002537 (April 2024) or subsequent relevant patches for CVE-2024-26229. If the CSC service is not required in the environment, it can be disabled as a defense-in-depth measure.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20596 | Windows 10 1607: 10.0.14393.6897 | Windows 10 1809: 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

  1. Open Windows Update Settings (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to download and install the latest security update
  3. Alternatively, manually download the security update from the Microsoft Update Catalog for your specific Windows version
  4. Restart the system after the update is installed
  5. Verify the update was installed by checking the installed updates list and confirming the build number matches or exceeds: 10.0.10240.20596 (1507), 10.0.14393.6897 (1607), 10.0.17763.5696 (1809), 10.0.19044.4291 (21h2), 10.0.19045.4291 (22h2), 10.0.22000.2899 (Win11 21h2), 10.0.22621.3447 (Win11 22h2), or 10.0.22631.3447 (Win11 23h2)

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 / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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