How severe is CVE-2026-27004?

No CVSS score has been assigned to CVE-2026-27004 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-27004?

CVE-2026-27004 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix CVE-2026-27004?

Update openclaw to 2026.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27004 is resolved across your whole dependency graph.

How do I detect CVE-2026-27004 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-27004 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-27004 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-27004 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-27004?

CVE-2026-27004 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 2th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-27004?

CVE-2026-27004 is classified as CWE-209 (CWE-209), CWE-346 (CWE-346). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-27004 published, and has it been updated?

CVE-2026-27004 was published on February 19, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-27004 — openclaw

Fix: openclaw/openclaw@c6c5343

CVE-2026-27004 is a CWE-209 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw session tool visibility hardening and Telegram webhook secret fallback

Also known asGHSA-6hf3-mhgc-cm65

Published

Feb 19, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27004.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs2th percentile — riskier than 2% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

132other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.4Mdownloads / week

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.15`npm install openclaw@2026.2.15`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.2.15

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27004 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## 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, pr

O3 Security · Impact-Aware SCA

Is CVE-2026-27004 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works