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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ff98-w8hj-qrxf can be triaged on real exposure rather than presence alone.

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

Not in CISA KEV

GHSA-ff98-w8hj-qrxf — openclaw

Fix: openclaw/openclaw@2e421f3

GHSA-ff98-w8hj-qrxf is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

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

Exploitation data as of Mar 4, 2026 · OSV.dev, 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.

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

openclawnpm

3.1Mdownloads / 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`npm install openclaw@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ff98-w8hj-qrxf can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-ff98-w8hj-qrxf across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works