CVE-2026-45813
Bluetooth NimBLE BASS buffer overflow can allow device compromise via paired devices.
Is CVE-2026-45813 being exploited?
Not confirmed. CVE-2026-45813 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-45813?
CVE-2026-45813 is rated High. 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-45813?
Yes. A fix has been recorded for CVE-2026-45813. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-45813 affect?
CVE-2026-45813 affects Apache NimBLE <= 1.9.0, Embedded devices using NimBLE (IoT, wearables, medical, industrial controllers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-45813?
Upgrade to Apache NimBLE 1.10.0; restrict BASS access and enforce strict pairing/authentication.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Malformed BASS Add/Modify Source PDUs can trigger stack buffer overflow/out-of-bounds read, enabling remote code execution or crash over Bluetooth (pairing required).
Immediate action required
- affected<= 1.9.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.