dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53804

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.10240.21128 / 10.0.14393.8422 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
Exposure of sensitive information to an unauthorized actor in Windows Kernel allows an authorized attacker to disclose information 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

This is a local information disclosure vulnerability in the Windows Kernel. An authorized (local) attacker can exploit this to expose sensitive information that should remain protected. The vulnerability stems from improper access controls within the kernel that allow a local user to access information they should not be able to view.

MitigationApply the Microsoft security update for CVE-2025-53804 through Windows Update or Microsoft Update Catalog once released. Prioritize workstations and servers with sensitive data or multi-user access configurations.

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.21128
Windows 10 1607Operating system
Affected:< 10.0.14393.8422
Windows 10 1809Operating system
Affected:< 10.0.17763.7792
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909
Windows 11 24h2Operating system
Affected:< 10.0.26100.6508

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 build number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the installed Windows version and build number
    Affected if The build number is below the threshold for your Windows release (see version-specific thresholds in CVE details)
  2. Identify exact Windows release
    Run 'winver' to confirm whether you are on Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, 24h2
    Affected if Your Windows release matches one of the affected versions listed in the CVE and the build is less than the specified threshold
  3. Compare against CVE version thresholds
    Reference the build thresholds: Windows 10 1507 requires <10.0.10240.21128, 1607 requires <10.0.14393.8422, 1809 requires <10.0.17763.7792, 21h2 requires <10.0.19044.6332, 22h2 requires <10.0.19045.6332; Windows 11 22h2 requires <10.0.22621.5909, 23h2 requires <10.0.22631.5909, 24h2 requires <10.0.26100.6508
    Affected if Your installed build number is lower than the threshold for your specific Windows release

You are affected if your Windows version and build number fall within any of the affected ranges listed in the CVE.

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.21128 / 10.0.14393.8422 / 10.0.17763.7792 or later
Fixed in 10.0.10240.2112810.0.14393.842210.0.17763.7792
Interim mitigation

Apply the Microsoft security update for CVE-2025-53804 through Windows Update or Microsoft Update Catalog once released. Prioritize workstations and servers with sensitive data or multi-user access configurations.

Recommended fix High confidence

Apply the appropriate Windows security update for your specific version (listed above) to reach the fixed build number

  1. Identify your current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows 10 1507: Apply KB5055527 (Build 10.0.10240.21128) or later
  3. For Windows 10 1607: Apply KB5055518 (Build 10.0.14393.8422) or later
  4. For Windows 10 1809: Apply KB5055523 (Build 10.0.17763.7792) or later
  5. For Windows 10 21h2: Apply KB5055525 (Build 10.0.19044.6332) or later
  6. For Windows 10 22h2: Apply KB5055519 (Build 10.0.19045.6332) or later
  7. For Windows 11 22h2: Apply KB5055522 (Build 10.0.22621.5909) or later
  8. For Windows 11 23h2: Apply KB5055520 (Build 10.0.22631.5909) or later
Caveat None expected; this is a routine security update with no functional changes

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-2025-53804 — 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-53804 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