CVE-2026-51244
Received Received - Intake

Buffer Overflow in schreibfaul1 ESP32-audioI2S

Vulnerability report for CVE-2026-51244, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-27

Last updated on: 2026-07-27

Assigner: MITRE

Description

schreibfaul1 ESP32-audioI2S 3.4.5 has a buffer overflow vulnerability in UnpackFrameHeader(). Multiple attacker-controlled index parameters are used to access static and heap table arrays without range limitation. Invalid index values lead to out-of-bounds memory writing and heap buffer overflow.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-27
Last Modified
2026-07-27
Generated
2026-07-28
AI Q&A
2026-07-27
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
schreibfaul1 esp32_audioi2s 3.4.5

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a heap buffer overflow in the ESP32-audioI2S library version 3.4.5, specifically in the UnpackFrameHeader() function of the MP3 decoder. It occurs when attacker-controlled index values from an MP3 bitstream are used to access arrays without proper range checks, leading to out-of-bounds memory writes and potential heap corruption.

Detection Guidance

Detecting this vulnerability requires analyzing the ESP32-audioI2S library for buffer overflows during MP3 decoding. Check for crashes or memory corruption when processing MP3 files. Monitor heap usage and look for out-of-bounds writes in the UnpackFrameHeader() function. Use static analysis tools like AddressSanitizer or Valgrind to detect memory issues during MP3 file processing.

Impact Analysis

An attacker could exploit this by sending a maliciously crafted MP3 file to a vulnerable device. This could result in arbitrary code execution or a denial-of-service condition, potentially allowing the attacker to take control of the device or crash it.

Compliance Impact

This vulnerability primarily impacts device security and reliability rather than directly violating compliance standards like GDPR or HIPAA. However, it could indirectly affect compliance by enabling arbitrary code execution or denial-of-service attacks on devices processing audio data, potentially leading to unauthorized access to sensitive information or disruption of critical services. Organizations using vulnerable ESP32-audioI2S devices may need to assess whether this risk aligns with their security and data protection policies.

Mitigation Strategies

Immediately update the ESP32-audioI2S library to a patched version if available. Avoid processing untrusted MP3 files on vulnerable devices. Implement input validation for MP3 frame headers to prevent out-of-bounds access. Use memory-safe programming practices and enable compiler protections like stack canaries and DEP.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-51244. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart