dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54104

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 in the Windows Defender Firewall Service allows a locally authorized attacker to elevate privileges by exploiting how the service handles objects of incompatible types. The vulnerability stems from the service not properly validating object types before use, potentially allowing memory corruption that can be leveraged for privilege escalation.

MitigationApply Microsoft security updates immediately upon release for Windows Defender Firewall Service. Review and limit local user permissions following least-privilege principles to reduce the attack surface.

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. Determine Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to retrieve the full build number including the 5-digit build (e.g., 10.0.19045.6332)
    Affected if Your build number is less than the corresponding threshold for your Windows release (1507 < 10240.21128, 1607 < 14393.8422, 1809 < 17763.7792, 21h2 < 19044.6332, 22h2 < 19045.6332, 22h2 < 22621.5909, 23h2 < 22631.5909, 24h2 < 26100.6508)
  2. Identify Windows release version
    Run 'winver' to see your specific Windows 10/11 release (such as 1507, 1607, 1809, 21h2, 22h2, 23h2, or 24h2) displayed in theAbout Windows dialog
    Affected if You are on any of the affected releases listed in the CVE and your build falls below the patched threshold for that release
  3. Verify Windows Defender Firewall service status
    Open Services.msc or run 'Get-Service MpsSvc' in PowerShell to check if the Windows Defender Firewall service (MpsSvc) is installed and running
    Affected if The service exists on your system (standard on all affected Windows versions); the vulnerability applies regardless of enabled/disabled state as it concerns internal object handling

You are affected if your Windows build version is lower than the patched build for your specific Windows release, regardless of firewall configuration.

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 Microsoft security updates immediately upon release for Windows Defender Firewall Service. Review and limit local user permissions following least-privilege principles to reduce the attack surface.

Recommended fix High confidence

Apply Windows security updates to reach the minimum fixed build number for your Windows version; the fixes are delivered through Microsoft's monthly cumulative updates (Patch Tuesday)

  1. Identify the Windows version and build number by running `winver` or `systeminfo` in Command Prompt
  2. Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install all available updates
  4. After installation, verify the build number matches or exceeds the fixed version for your Windows release: Windows 10 1507 should be 10.0.10240.21128 or higher, Windows 10 1607 should be 10.0.14393.8422 or higher, Windows 10 1809 should be 10.0.17763.7792 or higher, Windows 10 21h2 should be 10.0.19044.6332 or higher, Windows 10 22h2 should be 10.0.19045.6332 or higher, Windows 11 22h2 should be 1
  5. Restart the system if prompted to complete the update installation
Caveat Standard Windows update process with no expected breaking changes; updates are cumulative and include all prior security fixes

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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