A malformed Bluetooth connection request message can cause the BT122 to leak potentially sensitive information. See vulnerability B-E4 in the related paper below.
CVE-2026-65933
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 24(Track)EG Risk 24/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 8%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 13, 2026
Advisory Details (1)
Auto-updated Aug 13, 2026Vendor Advisories for CVE-2026-65933(1)
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 21× in last 7d / 28× 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.
- 2026-08-21 02:41 UTCEG score recompute
- 2026-08-21 02:41 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 04:39 UTCEG score recompute
- 2026-08-20 04:39 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 06:36 UTCEG score recompute
- 2026-08-19 06:36 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 08:32 UTCEG score recompute
- 2026-08-18 08:32 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 10:27 UTCEG score recompute
- 2026-08-17 10:27 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:25 UTCEG score recompute
- 2026-08-16 12:25 UTCGHSA enrichment
- 2026-08-15 14:23 UTCEG score recompute
- 2026-08-15 14:23 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 16:21 UTCGHSA enrichment
- 2026-08-13 18:18 UTCEG score recompute
- 2026-08-13 18:18 UTCGHSA enrichment
- 2026-08-13 17:27 UTCEG score recompute
- 2026-08-13 17:27 UTCGHSA enrichment
Show 3 moreShow fewer
- 2026-08-13 15:24 UTCEG score recompute
- 2026-08-13 15:13 UTCEG score recompute
- 2026-08-13 15:11 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-126
- CVE-2017-17772EG 9.8CRITICAL
- CVE-2022-1927NVD 7.8EG 9.8CRITICAL
- CVE-2019-3563EG 9.8CRITICAL
- CVE-2018-14790EG 9.8EPSS p92CRITICAL
- CVE-2017-7679EG 9.8EPSS p98CRITICAL
- CVE-2021-34584EG 9.1CRITICAL
- CVE-2019-11036EG 9.1EPSS p94CRITICAL
- CVE-2022-2175NVD 7.8EG 8.8HIGH
- CVE-2022-20823EG 8.6HIGH
- CVE-2022-20714EG 8.6HIGH
Frequently asked(5)
What is CVE-2026-65933?
When was CVE-2026-65933 disclosed?
Is CVE-2026-65933 actively exploited?
What is the CVSS score of CVE-2026-65933?
How do I remediate CVE-2026-65933?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65933
Is Your Infrastructure Affected by CVE-2026-65933?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.