In schreibfaul1 ESP32-audioI2S 3.4.5, a heap-based buffer overflow vulnerability exists in the ID3 tag parsing function showID3Tag() of the embedded audio streaming library. The program reads untrusted long ID3 tag value from malicious audio files and uses unbounded appendf() to write formatted strings into ps_ptr heap buffer without length validation. Successful exploitation allows attackers to execute arbitrary code, leak sensitive memory data, cause device crash, or escalate privileges via a crafted malicious audio file.
CVE-2026-51273
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; 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
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity78% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - 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-51273 at main · programmervuln/cveadvisory- · GitHub
https://github.com/programmervuln/cveadvisory-/blob/main/CVE-2026-51273ESP32-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-51273(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 9× in last 7d / 9× 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 08:35 UTCEG score recompute
- 2026-07-29 08:34 UTCGHSA enrichment
- 2026-07-28 20:45 UTCGHSA enrichment
- 2026-07-28 19:26 UTCEG score recompute▲ 7.80
- 2026-07-28 19:26 UTCGHSA enrichment
- 2026-07-28 19:24 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
- 2026-07-28 17:21 UTCNVD update
- 2026-07-28 16:54 UTCEG score recompute
- 2026-07-28 16:53 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-51273?
When was CVE-2026-51273 disclosed?
What is the CVSS score of CVE-2026-51273?
How do I remediate CVE-2026-51273?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-51273
Is Your Infrastructure Affected by CVE-2026-51273?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.