Quick answers
- Is CVE-2026-51261 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51261 being exploited in the wild.
- How severe is CVE-2026-51261?
- Informational severity, with a CVSS score of 0, published 28 July 2026.
- Which products and versions are affected?
- Schreibfaul1 ESP32-audioI2S 3.4.5.
- Is there a fix for CVE-2026-51261?
- A patch was published on 2026-07-28: Vendor patch reported as under development in external advisory Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-51261 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-51261?
- Check whether you run Schreibfaul1 ESP32-audioI2S 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 race condition (CWE-362) exists in the AudioBuffer::freeSpace() function within src/Audio.cpp of the ESP32-audioI2S library. The vulnerability is caused by missing mutex synchronization when accessing shared ring buffer pointers (m_readPtr and m_writePtr) during free space calculations. When the audio decoding task and I2S playback task execute concurrently, the function may return an overestimated free space value. An attacker can exploit this by providing a malicious audio stream or file, leading to a heap out-of-bounds write, memory corruption, and potentially remote arbitrary code execution. As of the advisory date, a vendor patch is reportedly under development.
Affected products
- schreibfaul1 ESP32-audioI2S 3.4.5
Timeline
- 2026-07-28: advisory: CVE-2026-51261 published
- 2026-07-28: patched: Vendor patch reported as under development in external advisory