dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-53810

MEDIUM · 6.7 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 →
69/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
Access of resource using incompatible type ('type confusion') in Windows Defender Firewall Service 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

A type confusion vulnerability exists in the Windows Defender Firewall Service where the service improperly handles resource access using incompatible types. This allows a locally authorized attacker to manipulate the service's behavior to elevate their privileges to higher levels on the affected system.

MitigationApply the Microsoft security update for CVE-2025-53810 through Windows Update or the Microsoft Update Catalog to patch the Windows Defender Firewall Service vulnerability.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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. Identify Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the exact Windows version and build number
    Affected if The displayed build number falls below the thresholds: 10240.21128 (1507), 14393.8422 (1607), 17763.7792 (1809), 19044.6332 (21h2), 19045.6332 (22h2), 22621.5909 (11 22h2), 22631.5909 (11 23h2), or 26100.6508 (11 24h2)
  2. Check Windows Defender Firewall Service status
    Open Services console (services.msc) or run 'Get-Service MpsSvc' in PowerShell to verify the Windows Defender Firewall Service (MpsSvc) is running
    Affected if The service exists and is running, as the vulnerability resides in this service
  3. Verify if security update KB5055527 is installed
    Run 'Get-HotFix | Where-Object {$_.HotFixID -eq "KB5055527"}' in PowerShell or check Windows Update history for this specific KB
    Affected if The hotfix KB5055527 is NOT installed, indicating the patch for CVE-2025-53810 has not been applied

A system is affected if it runs a Windows version within the specified build ranges AND the security update KB5055527 has not been 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.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-53810 through Windows Update or the Microsoft Update Catalog to patch the Windows Defender Firewall Service vulnerability.

Recommended fix High confidence

Install the relevant Microsoft security update for CVE-2025-53810. For each affected Windows version, the minimum fixed build is: Windows 10 1507: 10.0.10240.21128 | Windows 10 1607: 10.0.14393.8422 | Windows 10 1809: 10.0.17763.7792 | Windows 10 21h2: 10.0.19044.6332 | Windows 10 22h2: 10.0.19045.6

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually download the specific security update for this CVE from the Microsoft Update Catalog (search for CVE-2025-53810)
  4. Restart the computer after installing the updates
  5. Verify the update was installed by checking Windows Update history
Caveat Standard Windows security update with no expected breaking changes; as a local privilege escalation fix, this should be applied promptly

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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