# CVE-2026-76917: Wireshark Bluetooth AVRCP dissector heap buffer overflow

Source: https://junglewise.ai/threats/cve-2026-76917-wireshark-bluetooth-avrcp-dissector-heap-buffer-overflow  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-19. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-76917 · Severity: medium · CVSS 5.5 · Published 2026-08-19

Wireshark's Bluetooth AVRCP protocol analyzer contains a heap buffer overflow vulnerability triggered when processing specially crafted Bluetooth capture files or injected packets. An attacker can cause Wireshark to crash or potentially execute code by sending a series of vendor-dependent AVRCP fragments that cause integer overflow during reassembly. This affects users analyzing untrusted network captures or those exposed to malicious Bluetooth traffic.

Technologies: [Wireshark](https://junglewise.ai/threats/technologies/wireshark). Vendors: [Wireshark](https://junglewise.ai/threats/vendors/wireshark).

## Quick answers

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

**How severe is CVE-2026-76917?** Medium severity, with a CVSS score of 5.5, published 19 August 2026.

**Which products and versions are affected?** Wireshark 4.6.0 to 4.6.7, 4.4.0 to 4.4.17.

**Is there a fix for CVE-2026-76917?** A patch was published on 2026-08-12: Wireshark 4.6.8, 4.4.18 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-76917 attacked?** It is attacked over the network or with local access.

**Am I affected by CVE-2026-76917?** Check whether you run Wireshark 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 `dissect_vendor_dependent()` function in `packet-btavrcp.c` (lines 1195–1206), where a uint32_t accumulator tracking fragment payload lengths overflows when reassembling large numbers of fragments (e.g., 65,563 fragments × 65,511 bytes each wraps to ~130 KB). The undersized allocation is then overwritten by a 4 GiB memcpy, corrupting the heap and causing crash (SIGBUS) or potential code execution. The attack requires no user authentication and exploits standard Bluetooth protocol routing (H4→ACL→L2CAP→AVCTP→AVRCP), requiring only an attacker-controlled pcap file or injected Bluetooth packets. Patches are available in Wireshark 4.6.8, 4.4.18, and later.

## Affected products

- Wireshark Wireshark 4.6.0 to 4.6.7, 4.4.0 to 4.4.17

## Timeline

- 2026-08-12: disclosed
- 2026-08-12: patched: Wireshark 4.6.8, 4.4.18

## References

- [https://gitlab.com/wireshark/wireshark/-/work_items/21488](https://gitlab.com/wireshark/wireshark/-/work_items/21488)
- [https://www.wireshark.org/security/wnpa-sec-2026-91.html](https://www.wireshark.org/security/wnpa-sec-2026-91.html)

## Related threats

- [Wireshark USB HID dissector infinite loop in Usage range parsing](https://junglewise.ai/threats/cve-2026-96421-usb-hid-protocol-dissector-infinite-loop-and-memory-leak-in-4-6-0)
- [Wireshark pcapng file parser heap out-of-bounds read](https://junglewise.ai/threats/cve-2026-76929-wireshark-pcapng-file-parser-heap-out-of-bounds-read)
- [Wireshark Kerberos dissector heap buffer overflow](https://junglewise.ai/threats/cve-2026-76924-wireshark-kerberos-dissector-heap-buffer-overflow)
- [Wireshark CMS protocol dissector heap-use-after-free](https://junglewise.ai/threats/cve-2026-76921-wireshark-cms-protocol-dissector-heap-use-after-free)
- [Wireshark ESS protocol dissector crash via uninitialized pointer](https://junglewise.ai/threats/cve-2026-76919-wireshark-ess-protocol-dissector-crash-via-uninitialized-pointer)