CVE-2026-130603
9.3CriticalPublished 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
Critical
0CVSS v4.010
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-121, CWE-122, CWE-125
What an attacker gets
Remote attackers can trigger memory corruption or remote code execution by sending crafted Zenoh messages. No authentication or user interaction is required to exploit this vulnerability.
Root cause
The zenoh-pico library fails to validate the length of the Zenoh identifier (ZID) during timestamp deserialization, leading to buffer overflows.
Affected versions
Eclipse Zenoh zenoh-pico versions 0.7.2-rc through 1.10.1.
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade to zenoh-pico version 1.10.2 or later. If you cannot upgrade immediately, restrict network access to the Zenoh transport ports to trusted sources only.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Eclipse Zenoh's zenoh-pico implementation, versions 0.7.2-rc up to but excluding 1.10.2, does not validate the Zenoh identifier (ZID) length when deserializing timestamps. An attacker-controlled length greater than 16 causes an out-of-bounds write to a fixed 16-byte identifier buffer and causes the subsequent zero-fill operation to receive a negative length converted to a large unsigned size. Truncated timestamp inputs can also cause out-of-bounds reads or assertion failures. A remote attacker able to deliver crafted timestamp-bearing Zenoh messages through an accepted transport can cause memory corruption and denial of service, with potential remote code execution in builds lacking appropriate binary protections. This issue is fixed in version 1.10.2. Depending on the release and message-decoding path, the unchecked timestamp identifier length causes a heap-based or stack-based buffer overflow. Ordinary-frame network message decoding moved from heap-backed storage to stack-local storage in version 1.5.0. Earlier affected releases already contained stack-based decoding paths, including reassembled fragmented messages.
References
- https://github.com/eclipse-zenoh/zenoh-pico/commit/9198576fe69f6af66a2ab4f12f579f72208d7b28
- https://github.com/eclipse-zenoh/zenoh-pico/commit/f51284e46d6b09378fb6e5b37e07e2910683a40a
- https://github.com/eclipse-zenoh/zenoh-pico/pull/1345
- https://github.com/eclipse-zenoh/zenoh-pico/releases/tag/1.10.2
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/594
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/396
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/396