CVE-2026-130603
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.
AI Remediation Playbook Pro+
Get step-by-step remediation playbooks with specific commands, verification steps, and rollback procedures.
Upgrade to Pro+AI Attack Path AnalysisPro+
Visualize potential attack chains and lateral movement paths with AI-powered analysis.
AI Risk ForecastingPro+
Predict exploitation likelihood with AI-powered threat intelligence forecasting.
AI Compliance MappingPro+
Map vulnerabilities to compliance frameworks with AI-assisted gap analysis.
MITRE ATT&CK TechniquesThreat Intelligence
How attackers may exploit this vulnerability