Skip to content
MediumVulnerability

GHSA-6hf3-mhgc-cm65: OpenClaw session tool visibility hardening and Telegram webhook secret fallback

Published
Record updated
View JSON
Affected
  • openclaw < 2026.2.15
Fixed in
2026.2.15
  • released February 15, 2026, 2 days before disclosure
Known exploitation
Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
EPSS
0.1%

Summary

In shared-agent, multi-user deployments, OpenClaw session tools (`sessions_list`, `sessions_history`, `sessions_send`) allowed broader session targeting than some operators intended, which could expose transcript content across peer sessions. Separately, Telegram webhook mode did not fall back to the per-account `webhookSecret` when only the account-level secret was configured. Affected versions of npm `openclaw` are `<= 2026.2.14`.

Mitigation

Patched in `2026.2.15` (planned next release). Remediation adds and enforces `tools.sessions.visibility` (`self | tree | agent | all`) across session tools, defaulting to `tree`, keeps sandbox clamping so sandboxed runs can be restricted to spawned/session-tree visibility, and resolves the Telegram webhook secret from account config fallback in monitor webhook startup. Fix commit: `c6c53437f7da033b94a01d492e904974e7bda74c`.