How many CVEs have patched jpeg_parse_marker?

1 published CVEs changed jpeg_parse_marker in espressif/esp-idf, in 5 distinct patches totalling 19 changed lines, between 2026 and 2026.

What is the latest CVE that changed jpeg_parse_marker?

CVE-2026-55687 (ESF-IDF: Stack-Based Out-of-Bounds Write in JPEG Decoder DQT Marker Parsing), published 2026-07-10, changed lines 761 to 841 of components/esp_driver_jpeg/jpeg_decode.c.

How does jpeg_parse_marker compare to the rest of espressif/esp-idf?

espressif/esp-idf has 17 CVEs with a located fix in total; 1 of them changed jpeg_parse_marker.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

espressif/esp-idf

Function

jpeg_parse_marker

Name: jpeg_parse_marker in espressif/esp-idf: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

components/esp_driver_jpeg/jpeg_decode.c

Last patched July 10, 2026

1

CVEs

That changed this function

5

Distinct patches

Backports counted once

19

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

jpeg_parse_marker in espressif/esp-idf was changed by 1 published CVE fixes in 2026, in 5 distinct patches that added or removed 19 lines in total.

espressif/esp-idf has 17 CVEs with a located fix in total, so 6% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed jpeg_parse_marker, newest first, with the lines each fix touched.

ESF-IDF: Stack-Based Out-of-Bounds Write in JPEG Decoder DQT Marker Parsing
CVE-2026-55687 · lines 761–841 · +17 −2 in 3 hunks
High · CVSS 7.5
EPSS 0.7%2026-07-10

Get an alert when the next CVE fix lands in espressif/esp-idf, with the patched functions.

Monitor esp-idf CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1jpeg_decoder_get_infocomponents/esp_driver_jpeg/jpeg_decode.c1 CVEs · 5 patches2026

Other hotspots in the repository

Functions in espressif/esp-idf changed by the most CVE fixes.

jpeg_parse_dqt_marker2 CVEs · components/esp_driver_jpeg/jpeg_parse_marker.c jpeg_parse_appn_marker2 CVEs · components/esp_driver_jpeg/jpeg_parse_marker.c jpeg_parse_dht_marker2 CVEs · components/esp_driver_jpeg/jpeg_parse_marker.c protocomm_ble_cleanup2 CVEs · components/protocomm/src/transports/protocomm_ble.c prepare_write_event_env2 CVEs · components/protocomm/src/transports/protocomm_ble.c handle_to_handler2 CVEs · components/protocomm/src/transports/protocomm_ble.c

All patched functions in espressif/esp-idf

Frequently asked questions

Common questions about CVE fixes to jpeg_parse_marker.

How many CVEs have patched jpeg_parse_marker?: 1 published CVEs changed jpeg_parse_marker in espressif/esp-idf, in 5 distinct patches totalling 19 changed lines, between 2026 and 2026.
What is the latest CVE that changed jpeg_parse_marker?: CVE-2026-55687 (ESF-IDF: Stack-Based Out-of-Bounds Write in JPEG Decoder DQT Marker Parsing), published 2026-07-10, changed lines 761 to 841 of components/esp_driver_jpeg/jpeg_decode.c.
How does jpeg_parse_marker compare to the rest of espressif/esp-idf?: espressif/esp-idf has 17 CVEs with a located fix in total; 1 of them changed jpeg_parse_marker.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track espressif/esp-idf CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing