CVE-2026-130603 PUBLISHED

Assigner: eclipse
Reserved: 17.11.2026 Published: 17.11.2026 Updated: 17.11.2026

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.

Metrics

CVSS Vector: 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
CVSS Score: 9.3

Product Status

Vendor Eclipse Foundation
Product Eclipse Zenoh (zenoh-pico)
Versions Default: unaffected
  • affected from 0.7.2-rc to 1.10.2 (excl.)

Credits

  • Weiheng Qiu https://gitlab.eclipse.org/weihengqiu finder

References

Problem Types

  • CWE-121 CWE
  • CWE-122 CWE
  • CWE-125 CWE

Impacts

  • CAPEC-100