CVE-2026-130603: critical vulnerability in Eclipse Zenoh (zenoh-pico)
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.3epss 0.9%
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.
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
Affected products
Eclipse Foundation · Eclipse Zenoh (zenoh-pico)References
https://github.com/eclipse-zenoh/zenoh-pico/commit/9198576fe69f6af66a2ab4f12f579f72208d7b28https://github.com/eclipse-zenoh/zenoh-pico/commit/f51284e46d6b09378fb6e5b37e07e2910683a40ahttps://github.com/eclipse-zenoh/zenoh-pico/pull/1345https://github.com/eclipse-zenoh/zenoh-pico/releases/tag/1.10.2https://gitlab.eclipse.org/security/cve-assignment/-/work_items/594https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/396