CVE-2026-16101

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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.

Spoofing an already bonded device can force either RS9116W or SiWx917 to re-pair/bond with a rogue device. See V1 in BLERP paper below

CVSS v3
8.8
EG Score
8.8(high)
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
12%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

BLERP: BLE Re-Pairing Attacks and Defenses - NDSS Symposium

https://www.ndss-symposium.org/ndss-paper/blerp-ble-re-pairing-attacks-and-defenses/
generic

Rs9116 Ble Release Notes | Overview | RS9116 SDK | latest | Silicon Labs

https://docs.silabs.com/rs9116-wiseconnect/latest/wifibt-wc-release-notes/rs9116-ble-release-notes#bug-fixes
generic

Sisdk Wifible Ble Release Notes | Wi-Fi 6 + BLE (WiSeConnect) | Simplicity SDK Release Notes | latest | Silicon Labs

https://docs.silabs.com/sisdk-release-notes/latest/sisdk-wifi-release-notes/sisdk-wifible-ble-release-notes

Vendor Advisories for CVE-2026-16101(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 25× in last 7d / 32× 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-08-20 16:26 UTCGHSA enrichment
  2. 2026-08-20 03:41 UTCEG score recompute
  3. 2026-08-20 03:41 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 14:54 UTCGHSA enrichment
  6. 2026-08-19 02:09 UTCEG score recompute
  7. 2026-08-19 02:09 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 13:23 UTCGHSA enrichment
  10. 2026-08-18 00:35 UTCEG score recompute
  11. 2026-08-18 00:34 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 11:44 UTCGHSA enrichment
  14. 2026-08-16 22:53 UTCEG score recompute
  15. 2026-08-16 22:53 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 10:07 UTCEG score recompute
  18. 2026-08-16 10:07 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 21:22 UTCGHSA enrichment
  21. 2026-08-15 08:36 UTCEG score recompute
  22. 2026-08-15 08:36 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 19:50 UTCGHSA enrichment
  25. 2026-08-14 07:05 UTCGHSA enrichment
Show 7 more
  1. 2026-08-13 18:19 UTCEG score recompute
  2. 2026-08-13 18:19 UTCGHSA enrichment
  3. 2026-08-13 17:27 UTCEG score recompute
  4. 2026-08-13 17:27 UTCGHSA enrichment
  5. 2026-08-13 15:24 UTCEG score recompute
  6. 2026-08-13 14:22 UTCEG score recompute
  7. 2026-08-13 14:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16101?
CVE-2026-16101 is a high vulnerability published on August 13, 2026. Spoofing an already bonded device can force either RS9116W or SiWx917 to re-pair/bond with a rogue device. See V1 in BLERP paper below
When was CVE-2026-16101 disclosed?
CVE-2026-16101 was first published in the National Vulnerability Database on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16101 actively exploited?
CVE-2026-16101 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 88.4% of all scored CVEs.
What is the CVSS score of CVE-2026-16101?
CVE-2026-16101 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-16101?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16101, 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-16101

Explore →

Is Your Infrastructure Affected by CVE-2026-16101?

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

Start Free Scan →Browse All CVEs