Quick answers
- Is CVE-2026-51275 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51275 being exploited in the wild.
- How severe is CVE-2026-51275?
- 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-51275?
- 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-51275 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-51275?
- 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 heap-based buffer overflow (CWE-122) exists in the `Audio::read_MP3_Header()` function within `src/Audio.cpp`. The vulnerability is caused by a lack of length validation when parsing ID3v2 APIC (attached picture) metadata frames. An attacker can provide a malicious MP3 file with an oversized APIC frame size value, leading to an out-of-bounds write into the fixed-size `m_ID3Hdr.iBuff` heap buffer. This can result in PSRAM heap metadata corruption, leading to a device crash (watchdog reset) or potential remote code execution. As of the advisory date, a fix is reportedly under development.
Affected products
- schreibfaul1 ESP32-audioI2S 3.4.5
Timeline
- 2026-07-28: advisory: CVE-2026-51275 published