Every CVESearch/Get API key

CVE-2026-27004

OpenClaw session tool visibility hardening and Telegram webhook secret fallback

6.9 MediumFix available

OpenClaw is a personal AI assistant. Prior to version 2026.2.15, 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. In shared-agent, multi-user, less-trusted environments: session-tool access could expose transcript content across peer sessions. In single-agent or trusted environments, practical impact is limited. In Telegram webhook mode, account-level secret wiring could be missed unless an explicit monitor webhook secret override was provided. Version 2026.2.15 fixes the issue.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
None
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
None
Availability
None

Exploit likelihood

0.12%Up 0.1 points since Feb 20, 2026
90%50%10%1%

What each source reports

CVE List Score used6.9

OpenClaw session tool visibility hardening and Telegram webhook secret fallback

OpenClaw is a personal AI assistant. Prior to version 2026.2.15, 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. In shared-agent, multi-user, less-trusted environments: session-tool access could expose transcript content across peer sessions. In single-agent or trusted environments, practical impact is limited. In Telegram webhook mode, account-level secret wiring could be missed unless an explicit monitor webhook secret override was provided. Version 2026.2.15 fixes the issue.

Record
CVE-2026-27004
CVSS 4.0
6.9 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-209, CWE-346
Updated
2026-11-02
EUVDEUVD-2026-84106.9

OpenClaw is a personal AI assistant. Prior to version 2026.2.15, 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. In shared-agent, multi-user, less-trusted environments: session-tool access could expose transcript content across peer sessions. In single-agent or trusted environments, practical impact is limited. In Telegram webhook mode, account-level secret wiring could be missed unless an explicit monitor webhook secret override was provided. Version 2026.2.15 fixes the issue.

Record
EUVD-2026-8410
CVSS 4.0
6.9 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-6hf3-mhgc-cm656.9

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.

Record
GHSA-6hf3-mhgc-cm65
CVSS 4.0
6.9 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-209, CWE-346
Updated
2026-11-02
NVD6.9

OpenClaw is a personal AI assistant. Prior to version 2026.2.15, 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. In shared-agent, multi-user, less-trusted environments: session-tool access could expose transcript content across peer sessions. In single-agent or trusted environments, practical impact is limited. In Telegram webhook mode, account-level secret wiring could be missed unless an explicit monitor webhook secret override was provided. Version 2026.2.15 fixes the issue.

Record
CVE-2026-27004
CVSS 4.0
6.9 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness
CWE-209, CWE-346
Updated
2026-11-02
OSV6.9

OpenClaw session tool visibility hardening and Telegram webhook secret fallback

OpenClaw is a personal AI assistant. Prior to version 2026.2.15, 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. In shared-agent, multi-user, less-trusted environments: session-tool access could expose transcript content across peer sessions. In single-agent or trusted environments, practical impact is limited. In Telegram webhook mode, account-level secret wiring could be missed unless an explicit monitor webhook secret override was provided. Version 2026.2.15 fixes the issue.

Record
CVE-2026-27004
CVSS 4.0
6.9 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-209, CWE-346
Updated
2026-11-04
OSVGHSA-6hf3-mhgc-cm656.9

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.

Record
GHSA-6hf3-mhgc-cm65
CVSS 4.0
6.9 MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-209, CWE-346
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
openclaw
npm
before 2026.2.15
2026.2.15

History

History
RecordedChangedSources
factsOSV
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2026-27004 is a medium vulnerability (CVSS 6.9) in Openclaw, published February 18, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.12%, the 1st percentile. Fixed in openclaw 2026.2.15.

References

PagesAll vulnerabilitiesBrowseDocsSourcesGuideGet API key
MoveEnter Open