# 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) length


- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-fw6g-3fgh-f6m6

## What is CVE-2026-130603?

CVE-2026-130603 is a critical vulnerability in Eclipse Zenoh (zenoh-pico), published on 17 Nov 2026. 

### Official 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-122 (Heap-based Buffer Overflow), CWE-125 (Out-of-bounds Read), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-130603?


## How do I fix CVE-2026-130603?

No fix has been published for CVE-2026-130603 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130603 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130603 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130603 and fix it if it is affected.

What it is: CVE-2026-130603 is a critical vulnerability in Eclipse Zenoh (zenoh-pico), published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130603 exists.

Affected product: Eclipse Zenoh (zenoh-pico). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130603/ (Markdown: https://insights.sbomify.com/CVE-2026-130603/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130603
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130603
- OSV: https://osv.dev/vulnerability/CVE-2026-130603

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130603/
Summaries are generated and may contain mistakes; the official description above is the record.
