Eclipse Foundation · Eclipse Zenoh (zenoh-pico) · CWE-121 · CWE-122 · CWE-125 · published 2026-11-17

CVE-2026-130603

This month Public proof-of-concept exists (SSVC exploitation: poc).

CVE-2026-130603 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 0.9% chance of exploitation in the next 30 days, higher than 60% of all CVEs. This Eclipse Zenoh (zenoh-pico) vulnerability: CVSS 9.3 (v4.0), attacks can be automated, a successful attack gives total control of the component. Patch in your normal monthly cycle.

Share this

Remediation#

No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.9% (61th pct)FIRST EPSS v2026.06.15
CVSS base score9.3 (v4.0)
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
CNA / CISA ADP
SSVC exploitationpocCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Weakness: CWE-121: Stack-based Buffer Overflow · CWE-122: Heap-based Buffer Overflow · CWE-125: Out-of-bounds Read

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →