GHSA-6hf3-mhgc-cm65 CVE-2026-27004

OpenClaw session tool visibility hardening and Telegram webhook secret fallback

Medium npm

Severity: 0.0 / 10; Medium · CVSS 4.0
Exploit chance (EPSS): 0.12%; Chance of exploitation in the next 30 days. Higher than 1.69% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-209 Generation of Error Message Containing Sensitive Information; CWE-346 Origin Validation Error
Fix: 2026.2.15; Upgrade openclaw to this version or later

Description

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.

Affected versions

npm

Package	Vulnerable	Fixed in
openclaw	`< 2026.2.15`	`2026.2.15`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

openclaw npm → `2026.2.15`

npm

npm install openclaw@2026.2.15

yarn

yarn add openclaw@2026.2.15

pnpm

pnpm add openclaw@2026.2.15

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector: Local
Attack complexity: Low
Attack requirements: None
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): High
Integrity (vulnerable system): None
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

CVSS 3.1 5.5

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Weakness

CWE-209: Generation of Error Message Containing Sensitive Information

The product generates an error message that includes sensitive information about its environment, users, or associated data.

How to prevent it

Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
Implementation: Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation: Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
Implementation, Build and Compilation: Debugging information should not make its way into a production release.
Implementation, Build and Compilation: Debugging information should not make its way into a production release.
System Configuration: Where available, configure the environment to use less verbose error messages. For example, in PHP, disable the display_errors setting during configuration, or at runtime using the error_reporting() function.
System Configuration: Create default error pages or messages that do not leak any information.

CWE-346: Origin Validation Error

The product does not properly verify that the source of data or communication is valid.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2026-27004

Packages

github.com/openclaw/openclaw

Timeline

Feb 18, 2026 Published
Jun 17, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-3x84-qq85-fj65 OpenClaw: Browser CDP discovery could accept blocked WebSocket URLs	High	Also affects openclaw
GHSA-9c3v-684m-579c OpenClaw MCP SSE redirects could forward Authorization headers	Medium	Also affects openclaw
GHSA-f397-5vjw-v2c2 OpenClaw: Shell inline-command parsing could miss an allowlist check	High	Also affects openclaw
GHSA-rx78-29qr-5hq8 OpenClaw: Workspace-derived service PATH could influence trash command selection	High	Also affects openclaw
GHSA-ccwh-wwpp-6wg5 OpenClaw: Host environment sanitizer missed two Node.js control variables	High	Also affects openclaw
GHSA-985f-72mj-8gf7 OpenClaw: Tool group policy callers could accept unvalidated group IDs	Medium	Also affects openclaw
GHSA-9v8j-9c9g-w66c OpenClaw: Bootstrap token replay could widen pending pairing scopes	Medium	Also affects openclaw
GHSA-c226-q6fx-6j6c OpenClaw: macOS Swift exec allowlist missed combined POSIX inline flags	Medium	Also affects openclaw

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor