dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-59513

MEDIUM · 5.5 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 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
Out-of-bounds read in Windows Bluetooth RFCOM Protocol Driver 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

An out-of-bounds read vulnerability exists in the Windows Bluetooth RFCOMM Protocol Driver. The flaw allows a locally authorized attacker to read adjacent memory contents beyond buffer boundaries, potentially exposing sensitive information from kernel memory.

MitigationApply the Microsoft security update for CVE-2025-59513 when released. Monitor Windows Update for the applicable patch for your Windows version.

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 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2008Operating system
Affected:all versions= r2

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 version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build number. Compare the build (e.g., 14393, 17763, 19044, 19045, 22631, 26100, 26200) to the vulnerable version lists: Windows 10 1607 (<14393.8594), 1809 (<17763.8027), 21h2 (<19044.6575), 22h2 (<19045.6575), Windows 11 23h2 (<22631.6199), 24h2 (<26100.7092), 25h2 (<26200.7092), or Windows Server 2008 R2 (all versions).
    Affected if The installed Windows build number falls within any of the version ranges listed as vulnerable.
  2. Verify Bluetooth RFCOMM driver presence
    Open Device Manager, expand 'Bluetooth', and check if the 'RFCOMM Protocol Driver' or 'Bluetooth RFCOMM Protocol Driver' device is present. Alternatively, run 'Get-PnpDevice -Class Bluetooth' in PowerShell with admin privileges to list Bluetooth devices.
    Affected if The RFCOMM Protocol Driver device is listed in Device Manager, indicating the Bluetooth stack with vulnerable component is loaded.
  3. Confirm Bluetooth is enabled
    Run 'Get-PnpDevice -Class Bluetooth | Where-Object {$_.Status -eq "OK"}' in PowerShell or check the Bluetooth icon in the system tray. The vulnerability requires the Bluetooth driver to be active.
    Affected if Bluetooth is enabled and the RFCOMM driver is loaded and functional.
  4. Check for security update KB
    Run 'Get-HotFix | Where-Object {$_.Description -like "*Security Update*"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security updates. Search specifically for the KB addressing CVE-2025-59513 (check Microsoft Security Response Center for the specific KB number for your Windows version).
    Affected if The specific security update for CVE-2025-59513 is NOT installed.

A system is affected if it runs a vulnerable Windows version from the listed ranges AND has the Bluetooth RFCOMM driver loaded, and the corresponding security update for this CVE 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.14393.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply the Microsoft security update for CVE-2025-59513 when released. Monitor Windows Update for the applicable patch for your Windows version.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8594 | Windows 10 1809: 10.0.17763.8027 | Windows 10 21h2: 10.0.19044.6575 | Windows 10 22h2: 10.0.19045.6575 | Windows 11 23h2: 10.0.22631.6199 | Windows 11 24h2: 10.0.26100.7092 | Windows 11 25h2: 10.0.26200.7092 | Windows Server 2008: Microsoft no longer supports this

  1. Identify your Windows version by running 'winver' or 'systeminfo' from command prompt
  2. Navigate to the Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2025-59513
  3. Download and install the corresponding security update for your Windows version from Windows Update or the Microsoft Update Catalog
  4. Restart the system after applying the update to ensure the Bluetooth driver vulnerability is patched
  5. Verify the update was installed successfully by checking 'View update history' in Windows Update
Caveat Windows Server 2008 is end-of-life with no security updates available; requires operating system migration to a supported version

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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