limbo.watch

Likely permanent: GitHub doesn’t review this ecosystem

GHSA-v6r2-f6p2-88cj

esp_driver_jpeg (ESP-IDF) on other · published in espressif/esp-idf

Read the advisory on GitHub ↗

Facts

Severity
High · CVSS score 7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected versions (esp_driver_jpeg (ESP-IDF))
v6.0.1As entered by the maintainer. Not reviewed.
Fixed in (esp_driver_jpeg (ESP-IDF))
v6.0.2 (yet to be released)
Affected versions (esp_driver_jpeg (ESP-IDF))
v5.5.4As entered by the maintainer. Not reviewed.
Fixed in (esp_driver_jpeg (ESP-IDF))
v5.5.5 (yet to be released)
Affected versions (esp_driver_jpeg (ESP-IDF))
v5.4.4As entered by the maintainer. Not reviewed.
Fixed in (esp_driver_jpeg (ESP-IDF))
v5.4.5 (yet to be released)
Affected versions (esp_driver_jpeg (ESP-IDF))
v5.3.5As entered by the maintainer. Not reviewed.
Fixed in (esp_driver_jpeg (ESP-IDF))
v5.3.6 (yet to be released)
CVE
CVE-2026-55687 · published
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use esp_driver_jpeg (ESP-IDF) v6.0.1

The fixed-version field says “v6.0.2 (yet to be released)”. Check the advisory for which version fixes it. Dependabot, npm audit and OSV-Scanner probably never will.

Timeline

  1. 2026-06-22 16:00 UTC

    Published by the maintainers

    Cites CVE-2026-55687

  2. 2026-10-31 12:45 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  3. Not expected

    Reviewed by GitHub

    GitHub doesn’t review this ecosystem

Machine-readable record: feed/GHSA-v6r2-f6p2-88cj.json