Summary
OpenClaw session tool visibility hardening and Telegram webhook secret fallback
Vulnerability
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.
Typical Use Case Context
Most regular OpenClaw deployments run a single agent, or run in trusted environments. In those setups, practical risk from this issue is generally low.
Affected Packages / Versions
- Package: npm
openclaw - Affected versions:
<= 2026.2.14 - Patched version:
2026.2.15(planned next release)
Fix Commit(s)
c6c53437f7da033b94a01d492e904974e7bda74c
Thanks @aether-ai-agent for reporting.
Impact
- Shared-agent, multi-user, less-trusted environments: session-tool access could expose transcript content across peer sessions.
- Single-agent or trusted environments: practical impact is limited.
- Telegram webhook mode: account-level secret wiring could be missed unless an explicit monitor webhook secret override was provided.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Add and enforce
tools.sessions.visibility(self | tree | agent | all) across session tools, defaulting totree. - Keep sandbox clamping behavior so sandboxed runs can be restricted to spawned/session-tree visibility.
- Resolve Telegram webhook secret from account config fallback in monitor webhook startup.
Frequently Asked Questions
- What is CVE-2026-27004? CVE-2026-27004 is a medium-severity security vulnerability in openclaw (npm), affecting versions < 2026.2.15. It is fixed in 2026.2.15.
- Which versions of openclaw are affected by CVE-2026-27004? openclaw (npm) versions < 2026.2.15 is affected.
- Is there a fix for CVE-2026-27004? Yes. CVE-2026-27004 is fixed in 2026.2.15. Upgrade to this version or later.
- Is CVE-2026-27004 exploitable, and should I be worried? Whether CVE-2026-27004 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-27004 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-27004? Upgrade
openclawto 2026.2.15 or later.