dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-55692

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 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
Improper input validation in Windows Error Reporting allows an authorized attacker to elevate privileges locally.

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

Improper input validation in the Windows Error Reporting service allows a locally authenticated attacker to elevate from their current privileges to higher-level system privileges. The vulnerability stems from insufficient validation of user-supplied input within the Windows Error Reporting component, enabling local privilege escalation.

MitigationApply the relevant Microsoft security update for Windows Error Reporting once released. As this is a local privilege escalation, ensure systems are not left unattended and limit local user permissions where possible until the patch is deployed.

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.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:< 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

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
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full build number
    Affected if The build number is lower than any of the following: 10.0.10240.21161 (Windows 10 1507), 10.0.14393.8519 (Windows 10 1607), 10.0.17763.7919 (Windows 10 1809), 10.0.19044.6456 (Windows 10 21h2), 10.0.19045.6456 (Windows 10 22h2), 10.0.22621.6060 (Windows 11 22h2), 10.0.22631.6060 (Windows 11 23h2), o
  2. Verify Windows Error Reporting service status
    Open Services console (services.msc) or run 'Get-Service WerSvc' in PowerShell to check if the Windows Error Reporting service (WerSvc) is present and running
    Affected if The WerSvc service exists on the system (this is the vulnerable component)
  3. Confirm local user access
    Check for the presence of local user accounts by running 'net user' in Command Prompt or 'Get-LocalUser' in PowerShell
    Affected if Multiple local user accounts exist, especially non-administrative ones, as the attacker would need local authentication to exploit this LPE vulnerability

You are affected if your Windows build version is below the thresholds listed AND the Windows Error Reporting service is present on your system, enabling a locally authenticated attacker to perform privilege escalation.

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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply the relevant Microsoft security update for Windows Error Reporting once released. As this is a local privilege escalation, ensure systems are not left unattended and limit local user permissions where possible until the patch is deployed.

Recommended fix High confidence

Apply Microsoft security update (KB) for CVE-2025-55692; target builds: Windows 10 1507: 10.0.10240.21161 | Windows 10 1607: 10.0.14393.8519 | Windows 10 1809: 10.0.17763.7919 | Windows 10 21h2: 10.0.19044.6456 | Windows 10 22h2: 10.0.19045.6456 | Windows 11 22h2: 10.0.22621.6060 | Windows 11 23h2:

  1. 1. Open Windows Update on the affected system
  2. 2. Check for and install all pending security updates
  3. 3. Alternatively, manually download and install the appropriate Windows security update from Microsoft Update Catalog for the specific Windows version
  4. 4. After installation, restart the system to apply the changes
  5. 5. Verify the installed Windows version meets or exceeds the fixed build number for your Windows edition
Caveat Standard Windows security update; no expected breaking changes for this privilege escalation patch

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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