limbo.watch

Likely permanent: GitHub doesn’t review this ecosystem

GHSA-h7r3-gmg9-xjmg

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

Read the advisory on GitHub ↗

Facts

Severity
Medium · CVSS score 6.3CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
Affected versions (Protocomm BLE (ESP-IDF))
v5.5.2As entered by the maintainer. Not reviewed.
Fixed in (Protocomm BLE (ESP-IDF))
v5.5.3 (yet to be released)
Affected versions (Protocomm BLE (ESP-IDF))
v5.4.3As entered by the maintainer. Not reviewed.
Fixed in (Protocomm BLE (ESP-IDF))
v5.4.4 (yet to be released)
Affected versions (Protocomm BLE (ESP-IDF))
v5.3.4As entered by the maintainer. Not reviewed.
Fixed in (Protocomm BLE (ESP-IDF))
v5.3.5 (yet to be released)
Affected versions (Protocomm BLE (ESP-IDF))
v5.2.6As entered by the maintainer. Not reviewed.
Fixed in (Protocomm BLE (ESP-IDF))
v5.2.7 (yet to be released)
Affected versions (Protocomm BLE (ESP-IDF))
v5.1.6As entered by the maintainer. Not reviewed.
Fixed in (Protocomm BLE (ESP-IDF))
v5.1.7
CVE
CVE-2026-25507 · published
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
None found in the CVE List

If you use Protocomm BLE (ESP-IDF) v5.5.2

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

Timeline

  1. 2026-02-03 04:59 UTC

    Published by the maintainers

    Cites CVE-2026-25507

  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-h7r3-gmg9-xjmg.json