Disclosed weakness · no CVE recorded
OpenClaw could attach a worker after its caller lost authority
OpenClaw · OpenClaw · delegated cloud workers
First documented disclosure · Review checkpoint
Summary
A previously authorized request could finish attaching a worker and persist a credential after cancellation or replacement.
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 service did not revalidate caller authority after waiting to finish the attachment.
Conditions required
An authorized dispatch is waiting when the initiating run closes or is replaced.
Potential impact
A new worker attachment could survive the authority that requested it.
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 fix and reconcile worker attachments and credentials with active dispatches.
Operating lesson
Recheck authority when a queued action commits.
Evidence and limits
A broader September 2 change covered worker setup. The narrower attachment case was documented September 26.
Sources
- OpenClaw · fix(workers): prevent attachment after caller authority closes
Primary source ·
- OpenClaw 2026.11.4 stable release notes
Primary source ·