dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 4 Jul 2024. Known ransomware use
Windows 10 1507Operating system · Microsoft

CVE-2024-26169

HIGH · 7.8 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 →
96/100
Remediation priority · Urgent
In the wild Ransomware Zero-click Patch available

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 Error Reporting 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 Error Reporting Service. The vulnerability allows an authenticated attacker to gain elevated privileges by exploiting improper权限 handling in the service.

MitigationApply the Microsoft security update KB5002537 (or subsequent superseding patches) to address this vulnerability in the Windows Error Reporting Service component.

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 10 1809Operating system
Affected:< 10.0.17763.5576
Windows 10 21h2Operating system
Affected:< 10.0.19044.4170
Windows 10 22h2Operating system
Affected:< 10.0.19045.4170
Windows 11 21h2Operating system
Affected:< 10.0.22000.2836
Windows 11 22h2Operating system
Affected:< 10.0.22621.3296
Windows 11 23h2Operating system
Affected:< 10.0.22631.3296

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 the installed Windows version
    Run `winver` or `systeminfo | findstr /B /C:"OS Version"` and note the full build number (for example, 10.0.19044.4170)
    Affected if The build number falls below any of these thresholds: 10240.20526 (1507), 14393.6796 (1607), 17763.5576 (1809), 19044.4170 (21h2), 19045.4170 (22h2), 22000.2836 (Win11 21h2), 22621.3296 (Win11 22h2), or 22631.3296 (Win11 23h2)
  2. Confirm the Windows Error Reporting service exists
    Run `Get-Service -Name WerSvc -ErrorAction SilentlyContinue` or check Services.msc for 'Windows Error Reporting Service'
    Affected if The service exists on the system (the vulnerability is in this service)
  3. Check if the service is set to start automatically
    Run `Get-Service -Name WerSvc | Select-Object Name,StartType,Status`
    Affected if StartType is 'Automatic' or 'Manual' and the service is present (the service being disabled would prevent exploitation)
  4. Verify current user privileges
    Run `whoami /all` and note the group memberships and privileges listed
    Affected if The current user is a standard user without SYSTEM or administrative privileges (exploitation requires a standard user context to escalate from)
  5. Check if the vulnerability is patched by reviewing installed updates
    Run `Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10` and look for any March 2024 or later security updates
    Affected if No Microsoft security updates from March 2024 or later are installed (the patch was released in March 2024)

You are likely affected if your Windows build number is below the thresholds listed AND the Windows Error Reporting service is enabled AND you are running as a standard user on an unpatched 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.10240.20526 / 10.0.14393.6796 / 10.0.17763.5576 or later
Fixed in 10.0.10240.2052610.0.14393.679610.0.17763.5576
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update KB5002537 (or subsequent superseding patches) to address this vulnerability in the Windows Error Reporting Service component.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20526 or later | Windows 10 1607: 10.0.14393.6796 or later | Windows 10 1809: 10.0.17763.5576 or later | Windows 10 21h2: 10.0.19044.4170 or later | Windows 10 22h2: 10.0.19045.4170 or later | Windows 11 21h2: 10.0.22000.2836 or later | Windows 11 22h2: 10.0.22621.3296 or

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Note the Windows release (e.g., 10 1507, 10 1607, 10 1809, 10 21h2, 10 22h2, 11 21h2, 11 22h2, 11 23h2)
  3. Open Settings > Windows Update and check for updates, or manually download the appropriate cumulative update from the Microsoft Update Catalog for your specific Windows version
  4. Install the security update released for February 2024 (or later) that addresses CVE-2024-26169
  5. Restart the system when prompted to complete the installation
  6. Verify the installed version matches or exceeds the fixed build number for your Windows release using 'winver'
Caveat Standard Windows cumulative update; no expected breaking changes for this security patch

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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