CVE-2026-130603

Out-of-Bounds Buffer Overflow via Unvalidated Timestamp Identifier in Eclipse Zenoh

Published Nov 17, 2026 CVSS 4.0 · 9.3 Critical EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Eclipse Zenoh’s zenoh-pico implementation fails to validate the length of the Zenoh identifier (ZID) when deserializing timestamps. If an attacker supplies a length greater than 16 bytes, the buffer used to store the identifier is overflowed, causing both out‑of‑bounds writes and, depending on the execution path, out‑of‑bounds reads or assertion failures. The overflow can lead to memory corruption, including potential remote code execution in builds lacking sufficient binary protections, or it can crash the process and create a denial‑of‑service condition. The vulnerability is triggered by a crafted Zenoh message received over any accepted transport and is therefore reachable from a remote network attacker.

Affected Systems

The flaw affects Eclipse Foundation’s Eclipse Zenoh product, specifically the zenoh-pico library. All releases from version 0.7.2‑rc up to, but excluding, 1.10.2 are vulnerable. Versions prior to 1.10.2, including those that moved ordinary‑frame decoding to the stack in 1.5.0, contain the vulnerable logic.

Risk and Exploitability

The CVSS score of 9.3 classifies this flaw as critical. The EPSS score is not available, and it is not listed in the CISA KEV catalog. The attack can be performed remotely through the network transport layer by sending a specially crafted timestamp‑bearing Zenoh message. Because of the high severity, the likelihood of exploitation is significant in any environment where zenoh‑pico is exposed to untrusted peers.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade zenoh-pico to version 1.10.2 or later to apply the vendor fix.
  • If an immediate upgrade is not feasible, run the binary with hardened mitigations such as stack canaries, ASLR, and DEP to reduce the risk of successful code execution.
  • Implement additional validation to reject timestamps whose ZID length exceeds 16 bytes before reaching the deserialization logic, as a temporary safeguard.

Generated by OpenCVE AI on November 17, 2026 at 15:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title Out-of-Bounds Buffer Overflow via Unvalidated Timestamp Identifier in Eclipse Zenoh
Type Values Removed Values Added
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.
Weaknesses CWE-121
CWE-122
CWE-125
References
Metrics cvssV4_0

{'score': 9.3, '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'}

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Nov 17, 2026, 1:57 PM
Reserved
Nov 17, 2026, 12:46 PM
Status
Received
Published
Nov 17, 2026, 2:17 PM
Modified
Nov 17, 2026, 2:17 PM