In schreibfaul1 ESP32-audioI2S 3.4.5, a heap-based buffer overflow vulnerability exists in the WAV header parsing function read_WAV_Header(). The function reads untrusted chunk size and bytes-to-skip value directly from malicious WAV files without reasonable range restriction. Abnormally large bts and headerSize values lead to out-of-bounds heap memory read/write during header parsing, which can be exploited to execute arbitrary code, disclose sensitive information, cause denial of service or escalate privileges.
CVE-2026-51271
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.6; sources differ by 0.0.
- 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.6
- EG Score
- 9.6(high)
- EG Risk
- 59(Track*)EG Risk 59/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity96% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 28, 2026
Advisory Details (2)
Auto-updated Jul 28, 2026cveadvisory-/CVE-2026-51271 at main · programmervuln/cveadvisory- · GitHub
https://github.com/programmervuln/cveadvisory-/blob/main/CVE-2026-51271ESP32-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-51271(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 13× 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-07-29 13:41 UTCGHSA enrichment
- 2026-07-29 10:03 UTCGHSA enrichment
- 2026-07-29 06:25 UTCGHSA enrichment
- 2026-07-29 02:44 UTCGHSA enrichment
- 2026-07-28 23:05 UTCEG score recompute
- 2026-07-28 23:05 UTCGHSA enrichment
- 2026-07-28 19:27 UTCEG score recompute
- 2026-07-28 19:27 UTCGHSA enrichment
- 2026-07-28 18:24 UTCEG score recompute▲ 9.60
- 2026-07-28 18:22 UTCMITRE cvelistV5CVSS v3 → 9.6 · severity → CRITICAL
- 2026-07-28 16:19 UTCNVD update
- 2026-07-28 16:14 UTCEG score recompute
- 2026-07-28 16:13 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122
- CVE-2016-9603NVD 5.5EG 9.9EPSS p90CRITICAL
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2006-10002NVD 7.5EG 9.8CRITICAL
- CVE-2019-18323EG 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(4)
What is CVE-2026-51271?
When was CVE-2026-51271 disclosed?
What is the CVSS score of CVE-2026-51271?
How do I remediate CVE-2026-51271?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-51271
Is Your Infrastructure Affected by CVE-2026-51271?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.