How severe is GHSA-ff98-w8hj-qrxf?

No CVSS score has been assigned to GHSA-ff98-w8hj-qrxf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ff98-w8hj-qrxf?

GHSA-ff98-w8hj-qrxf affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-ff98-w8hj-qrxf?

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

How do I detect GHSA-ff98-w8hj-qrxf 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-ff98-w8hj-qrxf 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-ff98-w8hj-qrxf?

O3 pinpoints whether GHSA-ff98-w8hj-qrxf 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-ff98-w8hj-qrxf actively exploited in the wild?

No public exploit code has been indexed for GHSA-ff98-w8hj-qrxf 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.

When was GHSA-ff98-w8hj-qrxf published, and has it been updated?

GHSA-ff98-w8hj-qrxf was published on March 3, 2026 and was last updated on March 4, 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-ff98-w8hj-qrxf

OpenClaw plugin runtime command execution is part of trusted plugin boundary

Published

Mar 3, 2026

Updated

Mar 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

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

openclawnpm

3.7Mdownloads / week

Description

Summary

OpenClaw plugins/extensions run in-process and are treated as trusted code. This advisory tracks trust-boundary clarification around plugin runtime command execution (runtime.system.runCommandWithTimeout).

Impact

Plugins already execute with the same OS privileges as the OpenClaw process. Exposing runtime command helpers does not cross an additional sandbox boundary.

Affected Packages / Versions

Package: openclaw (npm)
Latest published version reviewed: 2026.2.17
Affected range for this advisory record: <= 2026.2.17
Planned patched version metadata: 2026.2.19 (next release line)

Fix Commit(s)

2e421f32dfc589c02706265fd3c3137ffc06c4b1

Remediation

Install only trusted plugins.
Use plugins.allow to pin explicit trusted plugin IDs.
SECURITY.md now explicitly documents that plugin runtime helpers are convenience APIs, not a sandbox boundary.

OpenClaw thanks @markmusson for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

### Summary OpenClaw plugins/extensions run in-process and are treated as trusted code. This advisory tracks trust-boundary clarification around plugin runtime command execution (`runtime.system.runCommandWithTimeout`). ### Impact Plugins already execute with the same OS privileges as the OpenClaw process. Exposing runtime command helpers does not cross an additional sandbox boundary. ### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version reviewed: `2026.2.17` - Affected range for this advisory record: `<= 2026.2.17` - Planned patched version metadata: `2026.

O3 Security · Impact-Aware SCA

Is GHSA-ff98-w8hj-qrxf in your dependencies?

O3 detects GHSA-ff98-w8hj-qrxf 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