schreibfaul1 ESP32-audioI2S v3.4.5 has an integer underflow vulnerability in the MP3Decoder::GetBits() function of the MP3 decoder due to unchecked bit reading operations. The lack of validation on the nBits parameter causes the cachedBits counter to underflow to negative values, leading to invalid bit manipulation, incorrect bitstream parsing, application crash, or arbitrary code execution via a specially crafted MP3 file.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-51254 as REJECTED on . It is no longer considered a valid vulnerability record. The original content below is preserved for historical reference only.
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2026-51254
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EchelonGraph score
- Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
- EG Score
- —
- EG Risk
- —
- EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 28, 2026
Advisory Details (2)
Auto-updated Jul 28, 2026cveadvisory-/CVE-2026-51254 at main · programmervuln/cveadvisory- · GitHub
https://github.com/programmervuln/cveadvisory-/blob/main/CVE-2026-51254ESP32-audioI2S/src/mp3_decoder/mp3_decoder.cpp at master · schreibfaul1/ESP32-audioI2S · GitHub
https://github.com/schreibfaul1/ESP32-audioI2S/blob/master/src/mp3_decoder/mp3_decoder.cppVendor Advisories for CVE-2026-51254(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 11:42 UTCGHSA enrichment
- 2026-08-27 13:27 UTCGHSA enrichment
- 2026-08-24 15:12 UTCGHSA enrichment
- 2026-08-21 16:56 UTCGHSA enrichment
- 2026-08-18 18:40 UTCGHSA enrichment
- 2026-08-15 17:01 UTCGHSA enrichment
- 2026-08-12 18:45 UTCGHSA enrichment
- 2026-08-09 20:30 UTCGHSA enrichment
- 2026-08-06 22:14 UTCGHSA enrichment
- 2026-08-03 23:59 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-08-01 01:43 UTCEG score recompute▼ 7.80
- 2026-08-01 01:43 UTCGHSA enrichment
- 2026-07-31 12:41 UTCGHSA enrichment
- 2026-07-30 23:39 UTCEG score recompute
- 2026-07-30 23:39 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 10:38 UTCEG score recompute
- 2026-07-30 10:37 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 21:32 UTCGHSA enrichment
- 2026-07-29 08:29 UTCEG score recompute
- 2026-07-29 08:29 UTCGHSA enrichment
- 2026-07-28 19:27 UTCEG score recompute
- 2026-07-28 19:27 UTCGHSA enrichment
Show 8 moreShow fewer
- 2026-07-28 18:59 UTCEG score recompute▲ 7.80
- 2026-07-28 18:59 UTCGHSA enrichment
- 2026-07-28 18:57 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
- 2026-07-28 16:24 UTCGHSA enrichment
- 2026-07-28 15:41 UTCGHSA enrichment
- 2026-07-28 15:37 UTCNVD update
- 2026-07-28 14:39 UTCEG score recompute
- 2026-07-28 14:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-191
Frequently asked(5)
What is CVE-2026-51254?
When was CVE-2026-51254 disclosed?
Is CVE-2026-51254 actively exploited?
What is the CVSS score of CVE-2026-51254?
How do I remediate CVE-2026-51254?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-51254
Is Your Infrastructure Affected by CVE-2026-51254?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.