CVE-2026-42975
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 · uneditedHeap-based buffer overflow in Windows Bluetooth Port Driver allows an unauthorized attacker to execute code over an adjacent network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 confidenceA heap-based buffer overflow vulnerability exists in the Windows Bluetooth Port Driver that allows an unauthenticated attacker with adjacent network access to execute arbitrary code. The overflow occurs in driver memory management, potentially allowing an attacker to corrupt heap metadata and achieve code execution with elevated privileges.
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< 10.0.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269all versions= r2CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version against affected rangesRun 'winver' or 'systeminfo | findstr /B /C:"OS"' to obtain the installed Windows version and build numberAffected if The version and build number fall within any of these ranges: Windows 10 1607 < 10.0.14393.9339, Windows 10 1809 < 10.0.17763.9020, Windows 10 21h2 < 10.0.19044.7548, Windows 10 22h2 < 10.0.19045.7548, Windows 11 24h2 < 10.0.26100.8875, Windows 11 25h2 < 10.0.26200.8875, Windows 11 26h1 < 10.0.28000
-
Determine if Bluetooth is enabledRun 'Get-PnpDevice -Class Bluetooth -Status OK' in PowerShell to list active Bluetooth devices, or check the Bluetooth service status via 'Get-Service bthserv'Affected if Bluetooth PnP devices show as 'OK' or the Bluetooth Support Service (bthserv) is running
-
Verify the Bluetooth Port Driver is loadedRun 'driverquery /v | findstr -i bluetooth' or check device manager for Bluetooth drivers (bthport.sys, bth.sys, or similar Bluetooth kernel drivers)Affected if The Windows Bluetooth Port Driver (bthport.sys) or related Bluetooth drivers are present and loaded in memory
-
Check for recent Bluetooth driver updatesRun 'Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceName -like "*Bluetooth*"} | Select-Object DeviceName, DriverVersion, DriverDate' to list installed Bluetooth driver versionsAffected if The driver version cannot be determined or is older than the patched versions corresponding to the Windows build numbers listed in the affected versions
A system is affected if it runs a vulnerable Windows version in the affected ranges AND has the Bluetooth Port Driver loaded with Bluetooth enabled, allowing adjacent network attackers to trigger the heap overflow in kernel-mode Bluetooth driver code.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.933910.0.17763.902010.0.19044.7548
Apply Microsoft security updates for the Windows Bluetooth Port Driver as they become available through Windows Update. Until a patch is released, consider disabling Bluetooth functionality on affected systems if not required, or limiting exposure by ensuring untrusted devices cannot access the adjacent network.
Windows 10 1607: 10.0.14393.9339 | Windows 10 1809: 10.0.17763.9020 | Windows 10 21h2: 10.0.19044.7548 | Windows 10 22h2: 10.0.19045.7548 | Windows 11 24h2: 10.0.26100.8875 | Windows 11 25h2: 10.0.26200.8875 | Windows 11 26h1: 10.0.28000.2269 | Windows Server 2012/R2: Latest available update
- Identify the Windows version and build number by running 'winver' or 'systeminfo'
- Open Windows Update by navigating to Settings > Update & Security > Windows Update
- Click 'Check for updates' and install all available security updates
- Alternatively, download the specific security update from the Microsoft Update Catalog (catalog.update.microsoft.com) by searching for the CVE number
- For Windows Server 2012/R2 which is End of Support, apply the latest available security update from Windows Update or contact Microsoft for Extended Security Updates (ESU)
- Restart the system after applying the update
- Verify the installed update by checking Windows Update history
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42975 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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