Disclosed weakness · no CVE recorded
OpenClaw could give a queued automation private memory after owner access was revoked
OpenClaw · OpenClaw · scheduled automation
First documented disclosure · Review checkpoint
Summary
A queued job could run with owner-private memory after its requester lost owner status.
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 workflow reused an earlier authorization decision when it eventually started.
Conditions required
A requester loses owner access between job admission and execution.
Potential impact
An automation could receive private context its requester could no longer access.
Affected versions and configurations
The upstream report identifies the affected behavior without specifying a complete version range.
Fix and mitigation status
OpenClaw lists this fix in 2026.11.5-beta.4, a prerelease. A stable fix was not verified.
Practical next steps
Use a build containing the fix. Review and cancel pending owner jobs when removing access on other builds.
Operating lesson
Re-evaluate access to sensitive context when a delayed job actually starts.
Evidence and limits
The sources establish stale authorization and its correction. They identify no confirmed unauthorized recipient.
Sources
- OpenClaw · Automation run keeps owner-private memory after its requester loses owner status while it waits for a run slot
Primary source ·
- OpenClaw · fix(cron): run keeps owner-private memory after its requester loses owner status
Primary source ·
- OpenClaw 2026.11.5-beta.4 prerelease notes
Primary source ·