Disclosed weakness · no CVE recorded
OpenClaw shared a side conversation with other viewers of the same session
OpenClaw · OpenClaw · Control UI side chats
First documented disclosure · Review checkpoint
Summary
Viewers of the same session could read what another person had written in its side chat.
Severity and exploitation evidence
No CVSS score recorded in this review.
Exploitation not established: The upstream sources document the behavior and correction. They identify no malicious use.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The side conversation belonged to the shared session regardless of who opened it.
Conditions required
Two people have access to the same primary session.
Potential impact
A user could disclose a private question or answer to other session viewers.
Affected versions and configurations
The upstream report identifies the affected behavior without specifying a complete version range.
Fix and mitigation status
The 2026.11.4 stable release includes this issue-specific correction.
Practical next steps
Deploy the correction and assign separate authenticated identities to people who need private side chats.
Operating lesson
Test private conversations with two independently authenticated viewers.
Evidence and limits
Clients sharing one authentication token still share an identity and its side conversation.
Sources
- OpenClaw · Control UI: make Side chat private per user instead of shared per session
Primary source ·
- OpenClaw · fix: other viewers see your Side chat in a shared session
Primary source ·
- OpenClaw 2026.11.4 stable release notes
Primary source ·