CVE-2026-102360 lib0 `readUint8Array` performs an unbounded read past the end of the decoder’s view, disclosing adjacent process memory

High 8.6 Published Updated

Remote attackers can read adjacent process memory via unbounded reads in lib0, exposing sensitive data like tokens and documents.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-102360?

CVE-2026-102360 is a high-severity vulnerability in dmonad lib0, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

A missing bounds check in the binary decoder in lib0, versions 0.2.1-0.2.117 and earlier and 1.0.0-rc.32 and earlier, lets any unauthenticated remote peer read adjacent process memory and receive it back. `readUint8Array` never compares the wire-supplied length against the decoder's own view, so one over-long length prefix returns whatever the host process allocated next: other tenants' document content, personal data, and live bearer session tokens**, recovered in full and at will. An attacker who can supply bytes to a lib0 decoder which means any peer that can open a socket, including before authentication reads adjacent process memory and, where the consumer echoes, stores or re-serves the decoded value, receives it back. This is patched in version 0.2.118 and 1.0.0-rc.33.

Weakness: CWE-125

Which versions are affected by CVE-2026-102360?

How do I fix CVE-2026-102360?

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

Is CVE-2026-102360 being exploited?

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

Sources

Also known as GHSA-r5c8-rf4w-qrq8.

Is CVE-2026-102360 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free