6.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-27004

CVE-2026-27004: 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.

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 Packages / Versions

Package: npm openclaw
Affected versions: <= 2026.2.14
Patched version: 2026.2.15 (planned next release)

Remediation

Add and enforce tools.sessions.visibility (self | tree | agent | all) across session tools, defaulting to tree.
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.

Fix Commit(s)

c6c53437f7da033b94a01d492e904974e7bda74c

Thanks @aether-ai-agent for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-27004

CVE-2026-27004:

6.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.2.15	2026.2.15

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The analysis of the security advisory and the associated commit c6c53437f7da033b94a01d492e904974e7bda74c reveals two distinct vulnerabilities. The primary vulnerability lies in the session management tools (sessions_list, sessions_history, sessions_send) of OpenClaw. These tools lacked proper access control, allowing any user in a shared-agent environment to list, view the history of, and send messages to sessions belonging to other users. This could lead to information disclosure and unauthorized actions. The patch addresses this by introducing a tools.sessions.visibility configuration option and implementing checks in the respective tool creation functions (createSessionsListTool, createSessionsHistoryTool, createSessionsSendTool). These functions were identified as vulnerable because they were modified to enforce these new security controls.

The second vulnerability was a configuration issue in the Telegram integration. The monitorTelegramProvider function failed to use a configured webhookSecret from the account settings as a fallback, potentially leaving the webhook unsecured. The patch corrects this by ensuring the secret is resolved correctly. This function is therefore also identified as vulnerable.

The identified functions are the precise locations where the vulnerabilities existed and were subsequently fixed. During runtime, these are the functions that would process potentially malicious requests, and their names would appear in profiler output during exploitation.

Vulnerable functions

createSessionsHistoryTool

src/agents/tools/sessions-history-tool.ts

The `execute` method within the tool created by this function was vulnerable as it did not perform visibility checks on the target session. This allowed a user to view the history of any session, even if they were not authorized, by providing the session key. The patch introduces a visibility check that restricts access based on the `tools.sessions.visibility` configuration, preventing unauthorized access to session history.

createSessionsListTool

src/agents/tools/sessions-list-tool.ts

The `execute` method within the tool created by this function was vulnerable because it listed sessions without considering visibility scopes. It would return a list of all sessions, potentially exposing the existence and metadata of sessions belonging to other users in a shared environment. The patch adds filtering logic to only include sessions that are within the configured visibility scope (`self`, `tree`, `agent`, or `all`).

createSessionsSendTool

src/agents/tools/sessions-send-tool.ts

The `execute` method within the tool created by this function was vulnerable because it allowed sending messages to any session without proper authorization checks. This could allow a user to inject messages into another user's session. The patch adds visibility checks to ensure that the requesting session has the permission to send messages to the target session, based on the `tools.sessions.visibility` setting.

monitorTelegramProvider

src/telegram/monitor.ts

This function was vulnerable because it did not correctly fall back to the per-account `webhookSecret` when one was not provided explicitly during monitor startup in Telegram webhook mode. This could lead to the webhook being configured without a secret, making it potentially vulnerable to unauthorized requests. The patch ensures that the account-level secret is used as a fallback.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.

6.9

-

Basic Information

Basic Information

Concerned about an active attack path?

CVE-2026-27004: OpenClaw session tool visibility hardening and Telegram webhook secret fallback

Vulnerability

Typical Use Case Context

Impact

Affected Packages / Versions

Remediation

Fix Commit(s)

CVE-2026-27004:

6.9

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

Basic Information

Basic Information

6.9

6.9

Technical Details

CVE-2026-27004: OpenClaw session tool visibility hardening and Telegram webhook secret fallback

Vulnerability

Typical Use Case Context

Impact

Affected Packages / Versions

Remediation

Fix Commit(s)

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI