Disclosed weakness · no CVE recorded
OpenClaw could turn a private draft into a shared conversation when copied
OpenClaw · OpenClaw · Control UI conversation forks
First documented disclosure · Review checkpoint
Summary
Copying a complete draft conversation could give the new copy shared visibility.
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 copy operation did not preserve the draft’s visibility setting.
Conditions required
A user makes a whole-conversation fork of a draft in a shared deployment.
Potential impact
Other authorized users of the shared space could read content intended to remain a draft.
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 inspect the visibility of older copies of private drafts.
Operating lesson
Preserve the source access policy when copying content.
Evidence and limits
The finding concerns the visibility of the resulting copy.
Sources
- OpenClaw · [Bug]: Whole-conversation forks turn Draft copies into Shared conversations
Primary source ·
- OpenClaw · fix: preserve Draft when copying conversations
Primary source ·
- OpenClaw 2026.11.4 stable release notes
Primary source ·