# CVE-2026-79377: Bestechnic BES2300 heap overflow in A2DP SBC decoder

Source: https://junglewise.ai/threats/cve-2026-79377-bestechnic-bes2300-heap-overflow-in-a2dp-sbc-decoder  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-08. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-79377 · Severity: high · CVSS 7.5 · Published 2026-09-08

The BES2300 is a Bluetooth audio system-on-chip used in wireless headphones and speakers. A heap overflow vulnerability in its audio decoding component allows an attacker to cause the device to crash or stop responding by sending a specially crafted Bluetooth packet, disrupting service for end users.

Technologies: [Bestechnic BES2300](https://junglewise.ai/threats/technologies/bes2300). Vendors: [Bestechnic](https://junglewise.ai/threats/vendors/bestechnic).

## Quick answers

**Is CVE-2026-79377 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-79377 being exploited in the wild.

**How severe is CVE-2026-79377?** High severity, with a CVSS score of 7.5, published 8 September 2026.

**Which products and versions are affected?** Bestechnic BES2300 v3.x and earlier.

**Is there a fix for CVE-2026-79377?** 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-79377 attacked?** It is attacked from the adjacent network, in device firmware.

**Am I affected by CVE-2026-79377?** 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

A heap buffer overflow exists in the a2dp_decoder_sbc.cpp component of Bestechnic BES2300 firmware v3.x and earlier. The vulnerability is triggered when processing SBC (Sub-Band Coding) audio frames over the L2CAP (Logical Link Control and Adaptation Protocol) layer used for Bluetooth audio streaming. An attacker with network proximity (Bluetooth range) can send a crafted L2CAP packet containing malicious audio data to cause heap memory corruption. This results in a denial of service condition via device crash or hang. The vulnerability requires no authentication and affects the audio decoding path that processes incoming Bluetooth audio streams.

## Affected products

- Bestechnic BES2300 v3.x and earlier

## Timeline

- 2026-09-08: disclosed

## References

- [https://github.com/Derek-Vencer/best1307/blob/296d587ad3766bbff96e7f466cf0775c170a/apps/audioplayers/a2dp_decoder/a2dp_decoder_sbc.cpp](https://github.com/Derek-Vencer/best1307/blob/296d587ad3766bbff96e7f466cf0775c170a/apps/audioplayers/a2dp_decoder/a2dp_decoder_sbc.cpp)
- [https://www.bestechnic.com/CVE-2026-79376.pdf](https://www.bestechnic.com/CVE-2026-79376.pdf)

## Related threats

- [Bestechnic BES2300 Bluetooth SoC denial of service in L2CAP handler](https://junglewise.ai/threats/cve-2026-79378-bestechnic-bes2300-bluetooth-soc-denial-of-service-in-l2cap)
- [Bestechnic BES2300 L2CAP denial of service](https://junglewise.ai/threats/cve-2026-79376-bestechnic-bes2300-l2cap-denial-of-service)