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.
This CVE has been withdrawn by MITRE
MITRE marked CVE-2026-51263 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-51263
- 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
- 36%
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 28, 2026
Advisory Details (2)
Auto-updated Sep 9, 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 2× 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-09-13 07:55 UTCGHSA enrichment
- 2026-09-10 14:34 UTCGHSA enrichment
- 2026-09-07 20:57 UTCGHSA enrichment
- 2026-09-04 12:09 UTCGHSA enrichment
- 2026-08-30 17:23 UTCGHSA enrichment
- 2026-08-28 00:01 UTCGHSA enrichment
- 2026-08-25 06:39 UTCGHSA enrichment
- 2026-08-22 13:10 UTCGHSA enrichment
- 2026-08-19 19:48 UTCGHSA enrichment
- 2026-08-17 00:36 UTCGHSA enrichment
- 2026-08-14 07:14 UTCGHSA enrichment
- 2026-08-11 13:53 UTCGHSA enrichment
- 2026-08-08 20:32 UTCGHSA enrichment
- 2026-08-06 03:10 UTCGHSA enrichment
- 2026-08-03 09:49 UTCGHSA enrichment
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 16:27 UTCEG score recompute▼ 9.80
- 2026-07-31 16:27 UTCGHSA enrichment
- 2026-07-31 12:06 UTCGHSA enrichment
- 2026-07-31 07:48 UTCGHSA enrichment
- 2026-07-31 03:30 UTCGHSA enrichment
- 2026-07-30 23:14 UTCGHSA enrichment
- 2026-07-30 18:57 UTCEG score recompute
- 2026-07-30 18:57 UTCGHSA enrichment
- 2026-07-30 16:28 UTCEPSS rescore
Show 21 moreShow fewer
- 2026-07-30 14:40 UTCGHSA enrichment
- 2026-07-30 10:12 UTCEG score recompute
- 2026-07-30 10:12 UTCGHSA enrichment
- 2026-07-30 05:55 UTCGHSA enrichment
- 2026-07-30 01:38 UTCEG score recompute
- 2026-07-30 01:38 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 21:11 UTCGHSA enrichment
- 2026-07-29 16:52 UTCGHSA enrichment
- 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 p91CRITICAL
- CVE-2017-20241EG 9.8CRITICAL
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2006-10002NVD 7.5EG 9.8CRITICAL
- CVE-2019-18296EG 9.8EPSS p92CRITICAL
- CVE-2019-18295EG 9.8EPSS p92CRITICAL
- CVE-2019-18293EG 9.8EPSS p92CRITICAL
- CVE-2019-18289EG 9.8EPSS p92CRITICAL
- CVE-2019-14901EG 9.8EPSS p97CRITICAL
- CVE-2019-14895EG 9.8EPSS p94CRITICAL
Frequently asked(5)
What is CVE-2026-51263?
When was CVE-2026-51263 disclosed?
Is CVE-2026-51263 actively exploited?
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.