CVE-2026-42975

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

July 14, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Jul 14, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42975

Vendor Advisories for CVE-2026-42975(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 34× in last 7d / 174× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 248 total refreshes for this CVE.

  1. 2026-08-30 05:17 UTCEG score recompute
  2. 2026-08-30 05:17 UTCVendor advisory
  3. 2026-08-30 05:17 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 23:39 UTCEG score recompute
  6. 2026-08-28 23:39 UTCVendor advisory
  7. 2026-08-28 23:39 UTCGHSA enrichment
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-28 02:01 UTCEG score recompute
  10. 2026-08-28 02:01 UTCVendor advisory
  11. 2026-08-28 02:00 UTCGHSA enrichment
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-27 13:31 UTCGHSA enrichment
  14. 2026-08-27 01:12 UTCEG score recompute
  15. 2026-08-27 01:12 UTCVendor advisory
  16. 2026-08-27 01:12 UTCGHSA enrichment
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-26 13:47 UTCVendor advisory
  19. 2026-08-26 13:47 UTCGHSA enrichment
  20. 2026-08-26 01:41 UTCEG score recompute
  21. 2026-08-26 01:41 UTCVendor advisory
  22. 2026-08-26 01:41 UTCGHSA enrichment
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-25 09:13 UTCVendor advisory
  25. 2026-08-25 09:13 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 21:27 UTCVendor advisory
  2. 2026-08-24 21:27 UTCGHSA enrichment
  3. 2026-08-24 15:14 UTCEG score recompute
  4. 2026-08-24 15:14 UTCVendor advisory
  5. 2026-08-24 15:14 UTCGHSA enrichment
  6. 2026-08-24 03:48 UTCVendor advisory
  7. 2026-08-24 03:48 UTCGHSA enrichment
  8. 2026-08-23 14:53 UTCVendor advisory
  9. 2026-08-23 14:53 UTCGHSA enrichment
  10. 2026-08-23 03:29 UTCEG score recompute
  11. 2026-08-23 03:29 UTCVendor advisory
  12. 2026-08-23 03:29 UTCGHSA enrichment
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 16:04 UTCVendor advisory
  15. 2026-08-22 16:03 UTCGHSA enrichment
  16. 2026-08-22 04:19 UTCEG score recompute
  17. 2026-08-22 04:19 UTCVendor advisory
  18. 2026-08-22 04:19 UTCGHSA enrichment
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 16:40 UTCGHSA enrichment
  21. 2026-08-21 04:40 UTCEG score recompute
  22. 2026-08-21 04:40 UTCVendor advisory
  23. 2026-08-21 04:40 UTCGHSA enrichment
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 17:13 UTCVendor advisory
  26. 2026-08-20 17:13 UTCGHSA enrichment
  27. 2026-08-20 16:04 UTCVendor advisory
  28. 2026-08-20 16:04 UTCGHSA enrichment
  29. 2026-08-20 04:37 UTCGHSA enrichment
  30. 2026-08-19 17:12 UTCEG score recompute
  31. 2026-08-19 17:12 UTCVendor advisory
  32. 2026-08-19 17:12 UTCGHSA enrichment
  33. 2026-08-19 17:03 UTCEPSS rescore
  34. 2026-08-19 15:55 UTCVendor advisory
  35. 2026-08-19 15:55 UTCGHSA enrichment
  36. 2026-08-19 05:26 UTCVendor advisory
  37. 2026-08-19 05:26 UTCGHSA enrichment
  38. 2026-08-18 17:48 UTCVendor advisory
  39. 2026-08-18 17:47 UTCGHSA enrichment
  40. 2026-08-18 16:57 UTCEG score recompute
  41. 2026-08-18 16:57 UTCVendor advisory
  42. 2026-08-18 16:57 UTCGHSA enrichment
  43. 2026-08-18 13:48 UTCEPSS rescore
  44. 2026-08-18 06:05 UTCGHSA enrichment
  45. 2026-08-17 17:59 UTCVendor advisory
  46. 2026-08-17 17:59 UTCGHSA enrichment
  47. 2026-08-17 13:48 UTCEG score recompute
  48. 2026-08-17 13:48 UTCGHSA enrichment
  49. 2026-08-17 13:47 UTCEPSS rescore
  50. 2026-08-17 02:24 UTCVendor advisory
  51. 2026-08-17 02:24 UTCGHSA enrichment
  52. 2026-08-16 14:59 UTCEG score recompute
  53. 2026-08-16 14:59 UTCVendor advisory
  54. 2026-08-16 14:59 UTCGHSA enrichment
  55. 2026-08-16 14:56 UTCEPSS rescore
  56. 2026-08-16 03:34 UTCEG score recompute
  57. 2026-08-16 03:34 UTCVendor advisory
  58. 2026-08-16 03:34 UTCGHSA enrichment
  59. 2026-08-16 02:14 UTCEPSS rescore
  60. 2026-08-15 16:10 UTCVendor advisory
  61. 2026-08-15 16:10 UTCGHSA enrichment
  62. 2026-08-15 04:45 UTCEG score recompute
  63. 2026-08-15 04:45 UTCVendor advisory
  64. 2026-08-15 04:45 UTCGHSA enrichment
  65. 2026-08-15 01:30 UTCEPSS rescore
  66. 2026-08-14 17:20 UTCVendor advisory
  67. 2026-08-14 17:20 UTCGHSA enrichment
  68. 2026-08-14 13:21 UTCVendor advisory
  69. 2026-08-14 13:21 UTCGHSA enrichment
  70. 2026-08-14 01:57 UTCEG score recompute
  71. 2026-08-14 01:57 UTCVendor advisory
  72. 2026-08-14 01:57 UTCGHSA enrichment
  73. 2026-08-13 22:00 UTCEPSS rescore
  74. 2026-08-13 14:32 UTCVendor advisory
  75. 2026-08-13 14:32 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-42975?
CVE-2026-42975 is a high vulnerability published on July 14, 2026. Heap-based buffer overflow in Windows Bluetooth Port Driver allows an unauthorized attacker to execute code over an adjacent network.
When was CVE-2026-42975 disclosed?
CVE-2026-42975 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42975 actively exploited?
CVE-2026-42975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.1% of all scored CVEs.
What is the CVSS score of CVE-2026-42975?
CVE-2026-42975 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-42975?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42975, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42975

Explore →

Is Your Infrastructure Affected by CVE-2026-42975?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.