CVE-2026-130603
Last modified
CVE-2026-130603 is a critical-severity vulnerability rated 9.3/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Eclipse Foundation | Eclipse Zenoh (zenoh-pico) | >= 0.7.2-rc, < 1.10.2 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-130603?
How severe is CVE-2026-130603?
How do I fix CVE-2026-130603?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-130593Scalar scalar-ninja 0.1.0 before 0.3.3 contains a cross-site…5.4
- CVE-2026-130594Scalar scalar-ninja 0.1.0 before 0.3.3 contains a cross-site…5.4
- CVE-2026-130595SQLBot 1.10.0 through 1.10.3 fails to apply its PostgreSQL d…5.9
- CVE-2026-130596FusionPBX through 5.6.5 contains a path traversal vulnerabil…4.8
- CVE-2026-1306The midi-Synth plugin for WordPress is vulnerable to arbitra…9.8
- CVE-2026-13060An authenticated user with limited read privileges may be ab…6.5
- CVE-2026-130608When using the admin area profile form to change ones profil…8.1
- CVE-2026-13061An authenticated user may be able to view session metadata b…4.3
- CVE-2026-130615Flowise through 3.1.4 contains a server-side request forgery…7.1
- CVE-2026-13062An authenticated user with write privileges on a Queryable E…6.5
- CVE-2026-130626The core JDK HTTP client (a2a-java-sdk-http-client) applies …7.5
- CVE-2026-130627The Vert.x HTTP client transport (a2a-java-sdk-http-client-v…7.5
Are you affected by CVE-2026-130603?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
