How severe is GHSA-h3f9-mjwj-w476?

GHSA-h3f9-mjwj-w476 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h3f9-mjwj-w476?

GHSA-h3f9-mjwj-w476 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-h3f9-mjwj-w476?

Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h3f9-mjwj-w476 is resolved across your whole dependency graph.

How do I detect GHSA-h3f9-mjwj-w476 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-h3f9-mjwj-w476 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-h3f9-mjwj-w476?

O3 pinpoints whether GHSA-h3f9-mjwj-w476 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-h3f9-mjwj-w476 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h3f9-mjwj-w476 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-h3f9-mjwj-w476?

GHSA-h3f9-mjwj-w476 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th 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-h3f9-mjwj-w476?

GHSA-h3f9-mjwj-w476 is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h3f9-mjwj-w476 published, and has it been updated?

GHSA-h3f9-mjwj-w476 was published on February 17, 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-h3f9-mjwj-w476

HIGH

OpenClaw Node host system.run rawCommand/command mismatch can bypass allowlist/approvals

Also known asCVE-2026-26325

Published

Feb 17, 2026

Updated

Feb 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk38th percentile+0.46%

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

Summary

A mismatch between rawCommand and command[] in the node host system.run handler could cause allowlist/approval evaluation to be performed on one command while executing a different argv.

Affected Configurations

This only impacts deployments that:

Use the node host / companion node execution path (system.run on a node).
Enable allowlist-based exec policy (security=allowlist) with approval prompting driven by allowlist misses (for example ask=on-miss).
Allow an attacker to invoke system.run.

Default/non-node configurations are not affected.

Impact

In affected configurations, an attacker who can invoke system.run can bypass allowlist enforcement and approval prompts by supplying an allowlisted rawCommand while providing a different command[] argv for execution.

Affected Packages / Versions

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

Fix

Enforce rawCommand/command[] consistency (gateway fail-fast + node host validation).

Fix Commit(s)

cb3290fca32593956638f161d9776266b90ab891

Release Process Note

This advisory pre-sets the patched version to the planned next release (2026.2.14). Once [email protected] is published to npm, the advisory can be published without further edits.

Thanks @christos-eth for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.14

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.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h3f9-mjwj-w476 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-h3f9-mjwj-w476 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-h3f9-mjwj-w476. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary A mismatch between `rawCommand` and `command[]` in the node host `system.run` handler could cause allowlist/approval evaluation to be performed on one command while executing a different argv. ## Affected Configurations This only impacts deployments that: - Use the node host / companion node execution path (`system.run` on a node). - Enable allowlist-based exec policy (`security=allowlist`) with approval prompting driven by allowlist misses (for example `ask=on-miss`). - Allow an attacker to invoke `system.run`. Default/non-node configurations are not affected. ## Impact In a

O3 Security · Impact-Aware SCA

Is GHSA-h3f9-mjwj-w476 in your dependencies?

O3 detects GHSA-h3f9-mjwj-w476 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