In schreibfaul1 ESP32-audioI2S 3.4.5, a heap-based buffer overflow vulnerability exists in the latinToUTF8() character encoding conversion function. The function calculates required buffer size by simply doubling input length and reallocates ps_ptr heap buffer without strict boundary validation. Malicious oversized input can trigger insufficient buffer allocation and out-of-bounds write during Latin-1 to UTF-8 conversion, leading to code execution, information disclosure, denial of service or privilege escalation.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-51272 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-51272
- 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
- 9.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
- 35%
- KEV
- Not listed
Published
July 30, 2026
Last Modified
July 30, 2026
Advisory Details (2)
Auto-updated Aug 20, 2026CVE-2026-51272 · GitHub
https://gist.github.com/programmervuln/5d1388bb85dfaf2e7e2700c5a2bceef5ESP32-audioI2S/src/Audio.cpp at master · schreibfaul1/ESP32-audioI2S · GitHub
https://github.com/schreibfaul1/ESP32-audioI2S/blob/master/src/Audio.cppVendor Advisories for CVE-2026-51272(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 2× in last 7d / 21× 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-19 06:48 UTCGHSA enrichment
- 2026-08-16 04:25 UTCGHSA enrichment
- 2026-08-13 02:02 UTCGHSA enrichment
- 2026-08-09 23:40 UTCGHSA enrichment
- 2026-08-06 21:18 UTCGHSA enrichment
- 2026-08-03 18:56 UTCEG score recompute
- 2026-08-03 18:56 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 16:33 UTCEG score recompute▼ 9.80
- 2026-07-31 16:33 UTCGHSA enrichment
- 2026-07-31 12:35 UTCGHSA enrichment
- 2026-07-31 08:36 UTCGHSA enrichment
- 2026-07-31 04:38 UTCGHSA enrichment
- 2026-07-31 00:40 UTCEG score recompute
- 2026-07-31 00:40 UTCGHSA enrichment
- 2026-07-30 20:43 UTCEG score recompute
- 2026-07-30 20:07 UTCEG score recompute▲ 9.80
- 2026-07-30 20:05 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-30 19:29 UTCNVD update
- 2026-07-30 17:56 UTCEG score recompute
- 2026-07-30 17:56 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122
- CVE-2016-9603NVD 5.5EG 9.9EPSS p91CRITICAL
- CVE-2017-20241EG 9.8CRITICAL
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2006-10002NVD 7.5EG 9.8CRITICAL
- CVE-2019-18296EG 9.8EPSS p91CRITICAL
- CVE-2019-18295EG 9.8EPSS p91CRITICAL
- CVE-2019-18293EG 9.8EPSS p91CRITICAL
- CVE-2019-18289EG 9.8EPSS p91CRITICAL
- CVE-2019-14901EG 9.8EPSS p97CRITICAL
- CVE-2019-14895EG 9.8EPSS p94CRITICAL
Frequently asked(5)
What is CVE-2026-51272?
When was CVE-2026-51272 disclosed?
Is CVE-2026-51272 actively exploited?
What is the CVSS score of CVE-2026-51272?
How do I remediate CVE-2026-51272?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-51272
Is Your Infrastructure Affected by CVE-2026-51272?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.