dbcve.org
Windows 10 21h2Operating system · Microsoft

CVE-2025-59290

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.19044.6332 / 10.0.19045.6332 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
Use after free in Windows Bluetooth 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

Use-after-free vulnerability in Windows Bluetooth Service enables a locally authorized attacker to elevate privileges. The vulnerability involves memory corruption where the service continues accessing freed memory, potentially allowing execution with elevated privileges.

MitigationApply the Microsoft security update for CVE-2025-59290 and verify Bluetooth functionality remains operational post-patch.

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 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
Windows Server 2022Operating system
Affected:< 10.0.20348.4106
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1849
Windows Server 2025Operating 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
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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 10.0.19044.6332)
    Affected if The build number is lower than the threshold for your Windows version (19044.6332 for 21h2, 19045.6332 for 10 22h2, 22621.5909 for 11 22h2, 22631.5909 for 11 23h2, 26100.6508 for 11 24h2/Server 2025, 20348.4106 for Server 2022, 25398.1849 for Server 2022 23h2)
  2. Identify Windows release version
    Run 'winver' to confirm whether your system is Windows 10 21h2, Windows 10 22h2, Windows 11 22h2, Windows 11 23h2, Windows 11 24h2, Windows Server 2022, Windows Server 2022 23h2, or Windows Server 2025
    Affected if Your system matches one of the affected product versions listed in the CVE
  3. Verify Bluetooth service presence
    Run 'Get-Service bthserv' in PowerShell or 'sc query bthserv' in Command Prompt to check if the Windows Bluetooth Service is installed
    Affected if The bthserv service exists on the system (the vulnerability resides in this service)
  4. Check if Bluetooth service is running
    Run 'Get-Service bthserv' or 'sc query bthserv' and examine the STATE field; running services show 'RUNNING'
    Affected if The bthserv service is currently running (the vulnerability is triggered when the service processes certain operations)

Your system is affected if it runs a Windows version within the affected product list AND the bthserv Bluetooth service is present and running, with a build number below the corresponding fixed version for your Windows release.

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.19044.6332 / 10.0.19045.6332 / 10.0.20348.4106 or later
Fixed in 10.0.19044.633210.0.19045.633210.0.20348.4106
Interim mitigation

Apply the Microsoft security update for CVE-2025-59290 and verify Bluetooth functionality remains operational post-patch.

Recommended fix High confidence

Upgrade to the minimum fixed version for your specific Windows release branch (as listed above) or migrate to a newer supported Windows release that includes the security patch

  1. Check current Windows version by running 'winver' or 'systeminfo' in command prompt
  2. Identify which Windows release branch you are on (e.g., 21h2, 22h2, 23h2, 24h2 for consumer; Server 2022, Server 2022 23h2, Server 2025 for Server)
  3. Apply the latest Windows Security Update from Windows Update or your organization's patch management system
  4. For Windows 10 21h2: ensure update to version 10.0.19044.6332 or later
  5. For Windows 10 22h2: ensure update to version 10.0.19045.6332 or later
  6. For Windows 11 22h2: ensure update to version 10.0.22621.5909 or later
  7. For Windows 11 23h2: ensure update to version 10.0.22631.5909 or later
  8. For Windows 11 24h2: ensure update to version 10.0.26100.6508 or later
Caveat Standard Windows update; ensure backups and test in staging environment before deploying broadly to production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 21h2 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-59290 — 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-59290 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