In some shared-agent deployments, OpenClaw session tools (sessions_list, sessions_history, sessions_send) allowed broader session targeting than some operators intended. This is primarily a configuration/visibility-scoping issue in multi-user environments where peers are not equally trusted.
In Telegram webhook mode, monitor startup also did not fall back to per-account webhookSecret when only the account-level secret was configured.
Most regular OpenClaw deployments run a single agent, or run in trusted environments. In those setups, practical risk from this issue is generally low.
openclaw<= 2026.2.142026.2.15 (planned next release)tools.sessions.visibility (self | tree | agent | all) across session tools, defaulting to tree.c6c53437f7da033b94a01d492e904974e7bda74cThanks @aether-ai-agent for reporting.
{
"github_reviewed": true,
"github_reviewed_at": "2026-02-18T22:43:53Z",
"severity": "MODERATE",
"nvd_published_at": "2026-02-20T00:16:17Z",
"cwe_ids": [
"CWE-209",
"CWE-346"
]
}