Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.9
CVE-2026-130603: Eclipse Zenoh zenoh-pico can be crashed remotely
CVE-2026-130603 · published 5 days ago
Summary
The lightweight Zenoh library (zenoh-pico) versions up to 1.10.1 fail to check the size of a field in incoming timestamps. A specially crafted message can overwrite memory, causing the application to stop working or, in some cases, run unwanted code. Update to version 1.10.2 or later to fix the issue.
What to do
- Update eclipse foundation eclipse zenoh (zenoh-pico) to version 1.10.2 or later.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| eclipse foundation | eclipse zenoh (zenoh-pico) | < 1.10.2 |
Original advisory text
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 le...
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.
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/9198576fe69f6af66a2ab4f12f579... Patch
- https://github.com/eclipse-zenoh/zenoh-pico/commit/f51284e46d6b09378fb6e5b37e07e... Patch
- https://github.com/eclipse-zenoh/zenoh-pico/pull/1345 Patch
- https://github.com/eclipse-zenoh/zenoh-pico/releases/tag/1.10.2 URL
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/594 URL
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/396 URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/130xxx/CVE-2026-1306... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-130603 Vendor Advisory
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Severity
9.9
Critical
Type
CWE-121Stack-based Buffer Overflow
CWE-122Heap-based Buffer Overflow
CWE-125Out-of-bounds Read
Timeline
Published17 Nov 2026
Updated21 Nov 2026
First seen17 Nov 2026
Track software like this
Free during beta