Disclosed weakness · no CVE recorded

OpenClaw could deliver a resumed Control UI reply to an earlier external chat

OpenClaw · OpenClaw

First documented disclosure · Review checkpoint

Summary

A reply resumed after plugin reload could leave the Control UI conversation and reach the external chat previously associated with the session.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reported behavior was observed in a project test. No unintended external delivery involving a user was documented in the reviewed sources.

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 handoff could inherit an older delivery destination instead of the audience for the active turn.

Conditions required

A Control UI session resumes a reply after a plugin reload and retains an earlier external chat route.

Potential impact

People in the earlier chat could receive content from the Control UI conversation.

Affected versions and configurations

The issue identifies a development revision on the main branch. Affected stable versions are unverified.

Fix and mitigation status

OpenClaw 2026.11.5-beta.2 lists the fix. A stable release containing this correction was not verified.

Practical next steps

Use a release containing the routing correction. Until then, avoid resuming sensitive Control UI conversations through this plugin-reload path.

Operating lesson

Bind a resumed reply to the audience of the turn that initiated it.

Evidence and limits

The November 2 report describes a project test on a development revision. The November 12 release is a prerelease.

Sources