CVE-2026-130603

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (60th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-127023 (ENISA EUVD) · GHSA-fw6g-3fgh-f6m6 (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
60th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 17, 2026

Last Modified

November 17, 2026

Advisory Details (6)

Auto-updated Nov 17, 2026
Patch available. Sources: github_commit, github_pr, github_release.
Web pageMentions a patch (unverified)

[Eclipse Zenoh] Buffer overflow in zenoh-pico message decoder with potential RCE (#594) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/594
GitHub commit

commit f51284e46d6b (eclipse-zenoh/zenoh-pico)

Fix landed in eclipse-zenoh/zenoh-pico commit f51284e46d6b — awaiting tagged release

https://github.com/eclipse-zenoh/zenoh-pico/commit/f51284e46d6b09378fb6e5b37e07e2910683a40a
GitHub release Patch Available

1.10.2

Patch available: eclipse-zenoh/zenoh-pico 1.10.2

https://github.com/eclipse-zenoh/zenoh-pico/releases/tag/1.10.2
GitHub commit

commit 9198576fe69f (eclipse-zenoh/zenoh-pico)

Fix landed in eclipse-zenoh/zenoh-pico commit 9198576fe69f — awaiting tagged release

https://github.com/eclipse-zenoh/zenoh-pico/commit/9198576fe69f6af66a2ab4f12f579f72208d7b28
GitHub pull request

Check for ZID bounds when deserializing timestamps

Fix merged in eclipse-zenoh/zenoh-pico PR #1345 on 2026-10-26 — awaiting tagged release

https://github.com/eclipse-zenoh/zenoh-pico/pull/1345
Web page

[Eclipse zenoh-pico] 3 Heap buffer overflow in ZenohID decode paths (message.c) (#396) · Issues · Eclipse Projects Security / vulnerability-reports · GitLab

https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/396

Vendor Advisories for CVE-2026-130603(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 03:41 UTCEchelonGraph re-scored
  2. 2026-11-22 03:41 UTCGHSA enrichmentGHSA-fw6g-3fgh-f6m6 · GitHub severity CRITICAL
  3. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  4. 2026-11-21 01:23 UTCEchelonGraph re-scored
  5. 2026-11-21 01:23 UTCGHSA enrichmentGHSA-fw6g-3fgh-f6m6 · GitHub severity CRITICAL
  6. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  7. 2026-11-19 23:08 UTCEchelonGraph re-scored
  8. 2026-11-19 23:07 UTCGHSA enrichmentGHSA-fw6g-3fgh-f6m6 · GitHub severity CRITICAL
  9. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  10. 2026-11-18 19:59 UTCEchelonGraph re-scored
  11. 2026-11-18 19:59 UTCGHSA enrichmentGHSA-fw6g-3fgh-f6m6 · GitHub severity CRITICAL
  12. 2026-11-18 16:34 UTCEPSS rescoreEPSS 1.0% · 64th percentile
  13. 2026-11-17 17:43 UTCEchelonGraph re-scored
  14. 2026-11-17 17:43 UTCGHSA enrichmentGHSA-fw6g-3fgh-f6m6 · GitHub severity CRITICAL
  15. 2026-11-17 17:18 UTCEchelonGraph re-scored
  16. 2026-11-17 17:18 UTCGHSA enrichmentGHSA-fw6g-3fgh-f6m6 · GitHub severity CRITICAL
  17. 2026-11-17 15:46 UTCGHSA enrichmentGHSA-fw6g-3fgh-f6m6 · GitHub severity CRITICAL
  18. 2026-11-17 15:03 UTCENISA EUVD ID recordedEUVD-2026-127023 · Source: ENISA EUVD
  19. 2026-11-17 14:28 UTCEchelonGraph re-scored
  20. 2026-11-17 14:03 UTCEchelonGraph re-scoredFirst assessed: 9.3 CRITICAL
  21. 2026-11-17 14:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-130603?
CVE-2026-130603 is a critical-severity vulnerability; its CVE record was published on November 17, 2026. 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…
When was the CVE record for CVE-2026-130603 published?
The CVE record for CVE-2026-130603 was published on November 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-130603 actively exploited?
CVE-2026-130603 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-130603?
CVE-2026-130603 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-130603?
A fix for CVE-2026-130603 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-130603 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-130603

Explore →

Is Your Infrastructure Affected by CVE-2026-130603?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.