dmonad lib0 up to 0.2.117/1.0.0-rc.32 Binary Decoder readUint8Array out-of-bounds

Summaryinfo

A vulnerability described as problematic has been identified in dmonad lib0 up to 0.2.117/1.0.0-rc.32. This affects the function readUint8Array of the component Binary Decoder. The manipulation results in out-of-bounds. This vulnerability is reported as CVE-2026-102360. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in dmonad lib0 up to 0.2.117/1.0.0-rc.32. Affected is the function readUint8Array of the component Binary Decoder. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-102360 since 09/29/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.

Upgrading to version 0.2.118 or 1.0.0-rc.33 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• dmonad

Name

• lib0

Version

• 0.2.117
• 1.0.0-rc.0
• 1.0.0-rc.1
• 1.0.0-rc.2
• 1.0.0-rc.3
• 1.0.0-rc.4
• 1.0.0-rc.5
• 1.0.0-rc.6
• 1.0.0-rc.7
• 1.0.0-rc.8
• 1.0.0-rc.9
• 1.0.0-rc.10
• 1.0.0-rc.11
• 1.0.0-rc.12
• 1.0.0-rc.13
• 1.0.0-rc.14
• 1.0.0-rc.15
• 1.0.0-rc.16
• 1.0.0-rc.17
• 1.0.0-rc.18
• 1.0.0-rc.19
• 1.0.0-rc.20
• 1.0.0-rc.21
• 1.0.0-rc.22
• 1.0.0-rc.23
• 1.0.0-rc.24
• 1.0.0-rc.25
• 1.0.0-rc.26
• 1.0.0-rc.27
• 1.0.0-rc.28
• 1.0.0-rc.29
• 1.0.0-rc.30
• 1.0.0-rc.31
• 1.0.0-rc.32

Website

• Product: https://github.com/dmonad/lib0/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion