dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54094

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

Type confusion vulnerability in Windows Defender Firewall Service allows a locally authorized attacker to exploit improper type handling to elevate privileges beyond their assigned permissions.

MitigationApply Microsoft security updates for Windows Defender Firewall Service immediately; verify the service functions correctly after patching.

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. Check Windows build version
    Run 'winver' from command prompt or 'systeminfo | findstr /B /C:"OS Version"' to retrieve the installed Windows build number
    Affected if The build number falls below any of these thresholds: 10240.21128 (Win10 1507), 14393.8422 (Win10 1607), 17763.7792 (Win10 1809), 19044.6332 (Win10 21h2), 19045.6332 (Win10 22h2), 22621.5909 (Win11 22h2), 22631.5909 (Win11 23h2), 26100.6508 (Win11 24h2)
  2. Identify Windows edition
    Run 'winver' or check System Properties to determine whether the system is Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, or 24h2
    Affected if The system matches any of the affected Windows 10 or 11 editions listed in the affected versions and the build is below the corresponding fix build
  3. Verify Windows Defender Firewall Service status
    Open Services console (services.msc) or run 'sc query MpsSvc' from elevated command prompt to check if Windows Defender Firewall service is running
    Affected if The MpsSvc (Windows Defender Firewall) service is present and running on the affected Windows version with a vulnerable build
  4. Confirm local user privileges
    Run 'whoami /priv' or check Local Users and Groups (lusrmgr.msc) to see current user account privileges
    Affected if A locally authorized user with limited permissions exists on the system, as the vulnerability allows privilege elevation beyond assigned permissions

The system is affected if it runs any of the listed Windows 10 or 11 versions with a build number lower than the fixed build for that version AND the Windows Defender Firewall service is running.

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 for Windows Defender Firewall Service immediately; verify the service functions correctly after patching.

Recommended fix High confidence

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.6332 | Windows 11 22h2: 10.0.22621.5909 | Windows 11 23h2: 10.0.22631.5909 | Windows 11 24h2: 10.0.26100.6508

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Open Windows Update by going to Settings > Update & Security > Windows Update
  3. Check for and install all pending security updates, specifically looking for the update addressing CVE-2025-54094
  4. If automatic updates are disabled, manually download the security update from the Microsoft Update Catalog (catalog.update.microsoft.com) by searching for the CVE number
  5. After installation, restart the system to ensure the security update is fully applied
  6. Verify the fix by checking that the Windows build number matches or exceeds the fixed version for your specific Windows release
Caveat Standard Windows security update with no expected breaking changes; updates are cumulative and include 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
  • 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-54094 — 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-54094 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