CVE-2026-42975 | Windows Bluetooth Port Driver Remote Code Execution

Heap-based buffer overflow in Windows Bluetooth Port Driver allows an unauthorized attacker to execute code over an adjacent network.

Published: 2026-07-14 Last update: 2026-07-16 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-42975 is rated Moderate Risk (41.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.34%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-42975

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-07-17 0.38% 0.34% -0.04%
2 2026-07-15 — 0.38% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-42975

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.0 3.1 HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.1 5.9 [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2026-42975

GitHub Security Advisory for CVE-2026-42975

GHSA-ggv4-x2vr-w9jf · Severity: high — Heap-based buffer overflow in Windows Bluetooth Port Driver allows an unauthorized attacker to...

Affected software / configurations for CVE-2026-42975

Vendor Product Version Raw CPE
microsoft windows_10_1607 < 10.0.14393.9339 cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x64:*
microsoft windows_10_1607 < 10.0.14393.9339 cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x86:*
microsoft windows_10_1809 < 10.0.17763.9020 cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x64:*
microsoft windows_10_1809 < 10.0.17763.9020 cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x86:*
microsoft windows_10_21h2 < 10.0.19044.7548 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:arm64:*
microsoft windows_10_21h2 < 10.0.19044.7548 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:x64:*
microsoft windows_10_21h2 < 10.0.19044.7548 cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:x86:*
microsoft windows_10_22h2 < 10.0.19045.7548 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:arm64:*
microsoft windows_10_22h2 < 10.0.19045.7548 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:x64:*
microsoft windows_10_22h2 < 10.0.19045.7548 cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:x86:*
microsoft windows_11_24h2 < 10.0.26100.8875 cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_24h2 < 10.0.26100.8875 cpe:2.3:o:microsoft:windows_11_24h2:*:*:*:*:*:*:x64:*
microsoft windows_11_25h2 < 10.0.26200.8875 cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:arm64:*
microsoft windows_11_25h2 < 10.0.26200.8875 cpe:2.3:o:microsoft:windows_11_25h2:*:*:*:*:*:*:x64:*
microsoft windows_11_26h1 < 10.0.28000.2269 cpe:2.3:o:microsoft:windows_11_26h1:*:*:*:*:*:*:arm64:*
microsoft windows_11_26h1 < 10.0.28000.2269 cpe:2.3:o:microsoft:windows_11_26h1:*:*:*:*:*:*:x64:*
microsoft windows_server_2012 — cpe:2.3:o:microsoft:windows_server_2012:-:*:*:*:*:*:*:*
microsoft windows_server_2012 r2 cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*
microsoft windows_server_2016 < 10.0.14393.9339 cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:-:*:x64:*
microsoft windows_server_2019 < 10.0.17763.9020 cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:-:*:x64:*
microsoft windows_server_2022 < 10.0.20348.5386 cpe:2.3:o:microsoft:windows_server_2022:*:*:*:*:*:*:x64:*
microsoft windows_server_2025 < 10.0.26100.33158 cpe:2.3:o:microsoft:windows_server_2025:*:*:*:*:*:*:x64:*

References for CVE-2026-42975

cvelogic Threat Intelligence