CVE-2026-102521

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (16th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The decoder in readFromDataView in lib0 before 0.2.119 can be tricked into reading more than it should from a buffer. The vulnerability allows reading past the decoders' view, thus exposing adjacent process memory. This can be anything that is currently in the head, for example credentials or logs. This is similar to but different from GHSA-r5c8-rf4w-qrq8.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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.3%
EPSS %ILE
16th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 29, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 49383f271628 (dmonad/lib0)

Patch available: dmonad/lib0 v0.2.119 (contains commit 49383f271628)

https://github.com/dmonad/lib0/commit/49383f2716283b90059dbfe01e110c0ab7ef5592
github Patch Available🟡 PoC Available

`readFromDataView` out-of-bounds read · Advisory · dmonad/lib0 · GitHub

https://github.com/dmonad/lib0/security/advisories/GHSA-g75x-89c3-rvmr

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-03 22:04 UTCEG score recompute
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-02 21:54 UTCEG score recompute
  4. 2026-10-01 21:44 UTCEG score recompute
  5. 2026-10-01 19:49 UTCEPSS rescore
  6. 2026-09-30 21:29 UTCEG score recompute
  7. 2026-09-30 20:27 UTCEG score recompute
  8. 2026-09-30 19:45 UTCEG score recompute
  9. 2026-09-30 15:02 UTCEPSS rescore
  10. 2026-09-29 14:18 UTCEG score recompute
  11. 2026-09-29 13:35 UTCEG score recompute
  12. 2026-09-29 13:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102521?
CVE-2026-102521 is a high vulnerability published on September 29, 2026. The decoder in readFromDataView in lib0 before 0.2.119 can be tricked into reading more than it should from a buffer. The vulnerability allows reading past the decoders' view, thus exposing adjacent process memory. This can be anything that is currently in the head, for example credentials or logs.…
When was CVE-2026-102521 disclosed?
CVE-2026-102521 was first published on September 29, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102521 actively exploited?
CVE-2026-102521 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102521?
CVE-2026-102521 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102521?
A fix for CVE-2026-102521 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-102521?

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

Book a Demo →Browse All CVEs