CVE-2026-102360: CWE-125: Out-of-bounds Read in dmonad lib0
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.
AI Analysis
Technical Summary
The vulnerability arises from a missing bounds check in the binary decoder of lib0, specifically in the readUint8Array function. This function does not verify that the wire-supplied length is within the decoder's view, allowing an attacker who can supply bytes to the decoder to read memory beyond the intended buffer. This memory can include sensitive information like document content, personal data, and live bearer session tokens. Any peer able to open a socket and supply data to the lib0 decoder can exploit this flaw, including before authentication. The issue is fixed in lib0 versions 0.2.118 and 1.0.0-rc.33.
Potential Impact
An unauthenticated remote attacker can read arbitrary adjacent process memory from the host running lib0, potentially exposing sensitive information such as other tenants' documents, personal data, and live session tokens. This leads to a confidentiality breach without requiring authentication or user interaction. The vulnerability does not impact integrity or availability.
Mitigation Recommendations
This vulnerability is patched in lib0 versions 0.2.118 and 1.0.0-rc.33. Users should upgrade to these or later versions to remediate the issue. There is no indication that any temporary mitigations or workarounds exist. Patch status is confirmed by the vendor advisory.
CVE-2026-102360: CWE-125: Out-of-bounds Read in dmonad lib0
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.
CVSS v3.1
Score 8.6high
Affected software
dmonad
lib0
pkg:github/dmonad/lib0Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from a missing bounds check in the binary decoder of lib0, specifically in the readUint8Array function. This function does not verify that the wire-supplied length is within the decoder's view, allowing an attacker who can supply bytes to the decoder to read memory beyond the intended buffer. This memory can include sensitive information like document content, personal data, and live bearer session tokens. Any peer able to open a socket and supply data to the lib0 decoder can exploit this flaw, including before authentication. The issue is fixed in lib0 versions 0.2.118 and 1.0.0-rc.33.
Potential Impact
An unauthenticated remote attacker can read arbitrary adjacent process memory from the host running lib0, potentially exposing sensitive information such as other tenants' documents, personal data, and live session tokens. This leads to a confidentiality breach without requiring authentication or user interaction. The vulnerability does not impact integrity or availability.
Mitigation Recommendations
This vulnerability is patched in lib0 versions 0.2.118 and 1.0.0-rc.33. Users should upgrade to these or later versions to remediate the issue. There is no indication that any temporary mitigations or workarounds exist. Patch status is confirmed by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-28T22:38:42.255Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6abbbe2df7a7c541067091cd
Added to database: 09/29/2026, 13:33:33 UTC
Last enriched: 09/29/2026, 13:47:49 UTC
Last updated: 09/29/2026, 18:20:13 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.