How severe is GHSA-6hf3-mhgc-cm65?

No CVSS score has been assigned to GHSA-6hf3-mhgc-cm65 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6hf3-mhgc-cm65?

GHSA-6hf3-mhgc-cm65 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-6hf3-mhgc-cm65?

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

How do I detect GHSA-6hf3-mhgc-cm65 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6hf3-mhgc-cm65 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.

How does O3 Security protect against GHSA-6hf3-mhgc-cm65?

O3 pinpoints whether GHSA-6hf3-mhgc-cm65 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6hf3-mhgc-cm65 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6hf3-mhgc-cm65 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 GHSA-6hf3-mhgc-cm65?

GHSA-6hf3-mhgc-cm65 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 1th 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 GHSA-6hf3-mhgc-cm65?

GHSA-6hf3-mhgc-cm65 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 GHSA-6hf3-mhgc-cm65 published, and has it been updated?

GHSA-6hf3-mhgc-cm65 was published on February 18, 2026 and was last updated on February 20, 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

GHSA-6hf3-mhgc-cm65

OpenClaw session tool visibility hardening and Telegram webhook secret fallback

Also known asCVE-2026-27004

Published

Feb 18, 2026

Updated

Feb 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk1th percentile+0.10%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / 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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hf3-mhgc-cm65 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.
How O3 protects you
O3 pinpoints whether GHSA-6hf3-mhgc-cm65 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6hf3-mhgc-cm65. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-6hf3-mhgc-cm65 in your dependencies?

O3 detects GHSA-6hf3-mhgc-cm65 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works