External risk intelligence

Eclipse Zenoh-pico Identifier Length Buffer Overflow

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130603

Eclipse Zenoh is a middleware/protocol used for distributed systems, robotics, and IoT. While it involves network communication, it is typically deployed within specific operational or internal application networks rather than as a public-facing internet service. Reachability depends heavily on specific deployment architecture, making internet exposure possible but not the default or intended state.

Out-of-bounds Read

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Eclipse Zenoh's zenoh-pico implementation allows remote attackers to cause memory corruption and denial of service, with a possibility of remote code execution. This issue stems from the system not properly validating the length of identifiers when processing timestamps, potentially leading to system instability or compromise if exploited.

  • Unchecked identifier lengths can crash systems.
  • Matters due to potential code execution risks.
  • Confirm relevance and exposure of this technology.

Attack Path

How an attacker could exploit the issue

An attacker can send specially crafted Zenoh messages over a network to trigger a vulnerability in Eclipse Zenoh's zenoh-pico implementation. This occurs when the system processes timestamp data without properly checking the length of the Zenoh identifier (ZID). If the attacker provides an excessively long ZID, it can lead to memory corruption and a denial-of-service condition, with the potential for remote code execution if certain security protections are absent.

  • Network access required.
  • Malformed timestamp messages trigger vulnerability.
  • Memory corruption and denial of service.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker could achieve memory corruption and denial of service by sending crafted Zenoh messages. This could potentially lead to remote code execution in specific builds.

  • Affects zenoh-pico's memory integrity.
  • Remote message delivery can trigger corruption.
  • Could enable unauthorized code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams responsible for Eclipse Zenoh deployments, likely platform or application owners, must first locate instances of zenoh-pico, assess their network exposure and business criticality, and identify the accountable owner. Subsequently, a remediation plan should be developed based on the identified risks and operational constraints.

  • Identify zenoh-pico deployment locations.
  • Verify network exposure and business criticality.
  • Plan remediation based on assessed risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Eclipse Zenoh-pico used for?

Eclipse Zenoh-pico is a lightweight implementation of the Zenoh protocol, a communication middleware designed for low-latency data exchange in distributed systems. It is commonly integrated into robotics, Internet of Things (IoT) sensors, and embedded environments where resource efficiency is critical for moving data between devices and applications.

What does CVE-2026-130603 mean for memory safety?

This vulnerability involves a failure to validate the length of Zenoh identifiers during timestamp deserialization, leading to buffer overflow conditions. Classified under CWE-121 (stack-based buffer overflow) and CWE-122 (heap-based buffer overflow), the flaw allows incoming data to overwrite adjacent memory, which can corrupt the system state, crash the application, or enable arbitrary code execution.

How does an attacker trigger this vulnerability?

An attacker triggers the bug by sending a crafted Zenoh message containing a ZID length greater than 16 bytes. If the message is accepted through a transport layer, the system attempts to process it, causing an out-of-bounds write or memory corruption. Note that simply receiving a valid or correctly formatted message does not trigger the flaw; it specifically requires the malicious, oversized identifier field.

Is my deployment at risk from this CVE?

According to the Halo Surface Signal, this software is typically deployed within specific internal or operational networks rather than as a public-facing service. While reachability depends on your unique architecture, any instance of zenoh-pico reachable over a network path—especially one accepting untrusted or external messages—is theoretically at higher risk than an isolated, internal-only instance.

What steps should I take to address CVE-2026-130603?

First, conduct an inventory to locate all instances of zenoh-pico across your infrastructure to determine which systems are active. Once identified, evaluate their network exposure and business impact. The primary resolution is to update the affected software components to version 1.10.2, where the validation logic for identifier lengths has been correctly implemented to prevent these overflows.

References