CVE-2026-81508 json
ESF-IDF: Heap Out-of-Bounds Read in Bluedroid A2DP Sink Media Packet Processing
published 2026-09-24 45 d ago modified 2026-09-25 45 d ago also EUVD-2026-86334
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. In 5.5.5, 6.0.1, and 6.1, the BlueDroid A2DP sink function btc_a2dp_sink_handle_inc_media() reads a timestamp field from the received media buffer before validating that the packet layout contains the field. A paired BR/EDR audio source within radio range can send a malformed A2DP media packet to a build with BlueDroid Classic Bluetooth and A2DP sink support enabled, causing an out-of-bounds read into adjacent heap memory and limited disclosure of heap contents. Arbitrary memory disclosure and code execution are not established.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 45 d ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- espressif esp-idf
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
- github.com /espressif/esp-idf/commit/0d118139ff8b7aa87b656c2f4a6421ecaa1f5939
- github.com /espressif/esp-idf/commit/6cb20db4dfeee81314d0c55acb82f3f0e7679abe
- github.com /espressif/esp-idf/commit/85d56bcd266117e0fe6a6b75511c8e122fda29ad
- github.com /espressif/esp-idf/commit/ca55d63de82e41e2c672bfd2b707fc80911f30ce
- github.com /espressif/esp-idf/security/advisories/GHSA-xcpr-5mqp-9qvv
Sources
- CVE List CVE-2026-81508
- NVD CVE-2026-81508
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.