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.3%, top 74% 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 — 5 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: 0%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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 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 35× in last 7d / 61× 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.

  1. 2026-07-29 09:33 UTCVendor advisory
  2. 2026-07-29 09:33 UTCGHSA enrichment
  3. 2026-07-28 22:08 UTCVendor advisory
  4. 2026-07-28 22:08 UTCGHSA enrichment
  5. 2026-07-28 16:34 UTCEG score recompute
  6. 2026-07-28 16:34 UTCVendor advisory
  7. 2026-07-28 16:34 UTCGHSA enrichment
  8. 2026-07-28 15:36 UTCEPSS rescore
  9. 2026-07-28 12:07 UTCVendor advisory
  10. 2026-07-28 12:07 UTCGHSA enrichment
  11. 2026-07-28 00:16 UTCVendor advisory
  12. 2026-07-28 00:16 UTCGHSA enrichment
  13. 2026-07-27 21:52 UTCVendor advisory
  14. 2026-07-27 21:52 UTCGHSA enrichment
  15. 2026-07-27 16:37 UTCEG score recompute
  16. 2026-07-27 16:37 UTCVendor advisory
  17. 2026-07-27 16:37 UTCGHSA enrichment
  18. 2026-07-27 14:13 UTCEPSS rescore
  19. 2026-07-27 05:05 UTCVendor advisory
  20. 2026-07-27 05:05 UTCGHSA enrichment
  21. 2026-07-26 17:30 UTCVendor advisory
  22. 2026-07-26 17:30 UTCGHSA enrichment
  23. 2026-07-26 16:34 UTCEG score recompute
  24. 2026-07-26 16:34 UTCVendor advisory
  25. 2026-07-26 16:34 UTCGHSA enrichment
Show 36 more
  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 05:06 UTCEG score recompute
  4. 2026-07-26 05:06 UTCVendor advisory
  5. 2026-07-26 05:06 UTCGHSA enrichment
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:17 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 03:12 UTCEG score recompute▲ 0.80
  10. 2026-07-22 16:51 UTCNVD updateCVSS v3 → 8.8
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 03:42 UTCEG score recompute
  16. 2026-07-19 03:42 UTCVendor advisory
  17. 2026-07-19 03:42 UTCGHSA enrichment
  18. 2026-07-19 02:29 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-17 02:25 UTCVendor advisory
  21. 2026-07-17 02:25 UTCGHSA enrichment
  22. 2026-07-16 22:05 UTCMITRE cvelistV5CVSS v3 → 8
  23. 2026-07-16 18:30 UTCNVD updateCVSS v3 → 8.8
  24. 2026-07-16 17:03 UTCEPSS rescore
  25. 2026-07-16 15:01 UTCVendor advisory
  26. 2026-07-16 15:01 UTCGHSA enrichment
  27. 2026-07-16 03:34 UTCVendor advisory
  28. 2026-07-16 03:34 UTCGHSA enrichment
  29. 2026-07-15 16:57 UTCEPSS rescore
  30. 2026-07-15 16:09 UTCVendor advisory
  31. 2026-07-15 16:09 UTCGHSA enrichment
  32. 2026-07-15 04:43 UTCVendor advisory
  33. 2026-07-15 04:43 UTCGHSA enrichment
  34. 2026-07-14 17:15 UTCEG score recompute
  35. 2026-07-14 17:15 UTCVendor advisory
  36. 2026-07-14 17:10 UTCMITRE cvelistV5first tracked

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 July 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 0% probability of exploitation in the next 30 days, which ranks it in the top 73.6% 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.

Start Free Scan →Browse All CVEs