schreibfaul1 ESP32-audioI2S 3.4.5 is vulnerable to Buffer Overflow. The Audio::openai_speech function in the Audio library manually constructs JSON request bodies and HTTP request headers by directly concatenating externally controllable input and instructions strings without effective length restriction and boundary validation. An unauthenticated remote attacker can send oversized malicious string data to trigger a heap buffer overflow during string splicing, resulting in memory corruption.
CVE-2026-51263
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.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
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
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 computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - 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-51263 at main · programmervuln/cveadvisory- · GitHub
https://github.com/programmervuln/cveadvisory-/blob/main/CVE-2026-51263ESP32-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-51263(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 12× in last 7d / 12× 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 12:35 UTCGHSA enrichment
- 2026-07-29 08:18 UTCGHSA enrichment
- 2026-07-29 04:01 UTCGHSA enrichment
- 2026-07-28 23:45 UTCEG score recompute
- 2026-07-28 23:44 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.80
- 2026-07-28 18:22 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-28 16:19 UTCNVD update
- 2026-07-28 15:30 UTCEG score recompute
- 2026-07-28 15:29 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-51263?
When was CVE-2026-51263 disclosed?
What is the CVSS score of CVE-2026-51263?
How do I remediate CVE-2026-51263?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-51263
Is Your Infrastructure Affected by CVE-2026-51263?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.