Skip to main content
Menu
CVEs

CVE

Eclipse Zenoh stack buffer overflow in ZID timestamp handling

CVE-2026-130603EUVD-2026-127023GHSA-FW6G-3FGH-F6M6

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

9.3CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 1.10.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.10.2.

Published
Last modified
Reference
Last checked
45/100 · provisional
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: poc
  • Automatable: yes
  • Technical impact: total

Summary

Eclipse Zenoh's zenoh-pico implementation does not check the length of the Zenoh identifier when reading timestamps. A remote attacker who can send crafted timestamp-bearing messages over the network, without logging in, can corrupt memory and crash the software, and in builds without proper binary protections this could lead to remote code execution.

Written by a model from the sources below. Verify against them.

Original 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.

cve.now Index

45Pcve.now Index 45 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.10.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130603 (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)…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130603 (entry last updated 2026-11-17):
Affected:
- Eclipse Foundation Eclipse Zenoh (zenoh-pico): from 0.7.2-rc, fixed in 1.10.2
Fixed versions: 1.10.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130603 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130603 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/396
- https://github.com/eclipse-zenoh/zenoh-pico/pull/1345
- https://github.com/eclipse-zenoh/zenoh-pico/commit/9198576fe69f6af66a2ab4f12f579f72208d7b28
- https://github.com/eclipse-zenoh/zenoh-pico/releases/tag/1.10.2
- https://github.com/eclipse-zenoh/zenoh-pico/commit/f51284e46d6b09378fb6e5b37e07e2910683a40a
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/594
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130603
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130603"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

  • Eclipse Foundation Eclipse Zenoh (zenoh-pico)

    From 0.7.2-rc · fixed in 1.10.2

Evidence 8

Vendor advisory · 2

Establishes: Affected and fixed versions.

  1. Link
  2. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Repository
  2. Repository
  3. Repository
  4. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130603

Is CVE-2026-130603 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130603?

Eclipse Zenoh (zenoh-pico): from 0.7.2-rc before 1.10.2.Source: cve.now feed data

How do I fix CVE-2026-130603?

Upgrade to a fixed version: 1.10.2.Source: cve.now feed data

More CVEs