CVE-2026-55687 json
ESF-IDF: Stack-Based Out-of-Bounds Write in JPEG Decoder DQT Marker Parsing
published 2026-07-10 4 mo ago modified 2026-10-25 15 d ago also EUVD-2026-42939
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
ESF-IDF is the Espressif Internet of Things (IOT) Development Framework. Versions 6.0.1, 5.5.4, 5.4.4, 5.3.5, and possibly prior contain an out-of-bounds write in jpeg_parse_dqt_marker() in components/esp_driver_jpeg/jpeg_parse_marker.c because the attacker-controlled DQT marker Tq nibble is used as an index into the qt_tbl array without validating that it is in the range 0..3, allowing malformed JPEG input to corrupt stack memory and reliably trigger a denial of service. This issue is fixed in version 6.0.2 and is expected to be fixed in versions 5.5.5, 5.4.5, and 5.3.6.
Patch / fix
- espressif esp-idf 6.0.2
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- espressif esp-idf
Classification
References
- github.com /espressif/esp-idf/commit/303c01305acb8ae5c4eb24a1786300681b4822a4
- github.com /espressif/esp-idf/commit/6ffafe8e93142ef8ffe51a6311d4abfc0f10fe77
- github.com /espressif/esp-idf/commit/7ccfc00f39faf1b7e5919f45b56fe44ba699d7c1
- github.com /espressif/esp-idf/commit/82c5c2dad45313786fb7e973059bc9094d95c3b2
- github.com /espressif/esp-idf/commit/f2df45bcedef11354e83c31a9718d680a68422c4
- github.com /espressif/esp-idf/security/advisories/GHSA-v6r2-f6p2-88cj
- github.com /espressif/esp-idf/releases/tag/v6.0.2
Sources
- CVE List CVE-2026-55687
- NVD CVE-2026-55687
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.