Skip to content
Threat Brief

← All advisories

CVE-2026-130603

Critical 9.3No known exploitationFix status unknown

Title not yet published

Record last updated

CVSS score

9.3

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.9%

Higher than 61% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-121, CWE-122, CWE-125

Patching and mitigation

Patch status
Unknown: no source documents a fix
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

No affected products documented yet.

Timeline

  1. No dated events documented yet.

Vendor guidance and references