Skip to content
IoT

CVE-2026-19293

8.8
High
EPSS 0.13%Aug 14, 2026

Bluetooth SMP omits max key size, allowing weaker keys and easier brute-force of BLE link keys.

common questions

Is CVE-2026-19293 being exploited?

Not confirmed. CVE-2026-19293 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-19293?

CVE-2026-19293 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-19293?

Not known from our data. No patch reference has been recorded for CVE-2026-19293, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-19293 affect?

CVE-2026-19293 affects Bluetooth Low Energy peripherals, BLE stacks/firmware (device vendors), IoT devices, Wearables, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19293?

Apply vendor firmware updates when released; restrict BLE pairing; unpair untrusted devices; monitor BLE activity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Bluetooth Low Energy peripheralsBLE stacks/firmware (device vendors)IoT devicesWearablesMedical/embedded BLE devices
impact

Local/adjacent attacker can force or accept smaller BLE keys, enabling offline brute-force to recover link keys, decrypt traffic, spoof or take over devices.

action required

Patch when possible

affected versions
silabs.com WiseConnect
  • affected>= 4.0.0 and < 4.1.0
  • affected>= 2.0.0 and < 2.14.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free