Quick answers
- Is CVE-2026-79376 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-79376 being exploited in the wild.
- How severe is CVE-2026-79376?
- High severity, with a CVSS score of 8.8, published 8 September 2026.
- Which products and versions are affected?
- Bestechnic BES2300 3.x and earlier.
- Is there a fix for CVE-2026-79376?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-79376 attacked?
- It is attacked from the adjacent network, in device firmware.
- Am I affected by CVE-2026-79376?
- Check whether you run Bestechnic BES2300 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the l2cap_handle_data() function within the BES2300 Bluetooth audio SoC firmware version 3.x and earlier. It is triggered by receiving a malformed L2CAP (Logical Link Control and Adaptation Protocol) packet over a Bluetooth connection. An attacker within Bluetooth range can send the crafted packet without requiring prior authentication or pairing. Successful exploitation results in a denial of service condition, causing the audio device to hang or reset. The vulnerability is classified as a memory handling or input validation flaw in the L2CAP packet processing logic.
Affected products
- Bestechnic BES2300 3.x and earlier
Timeline
- 2026-09-08: disclosed