How severe is GHSA-vmqr-rc7x-3446?

GHSA-vmqr-rc7x-3446 has a CVSS score of 6.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vmqr-rc7x-3446?

GHSA-vmqr-rc7x-3446 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-vmqr-rc7x-3446?

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

How do I detect GHSA-vmqr-rc7x-3446 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-vmqr-rc7x-3446 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-vmqr-rc7x-3446?

O3 pinpoints whether GHSA-vmqr-rc7x-3446 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-vmqr-rc7x-3446 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vmqr-rc7x-3446 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-vmqr-rc7x-3446?

GHSA-vmqr-rc7x-3446 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th 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-vmqr-rc7x-3446?

GHSA-vmqr-rc7x-3446 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-vmqr-rc7x-3446 published, and has it been updated?

GHSA-vmqr-rc7x-3446 was published on March 3, 2026 and was last updated on March 18, 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-vmqr-rc7x-3446

MEDIUM

OpenClaw's non-default safeBins sort configuration can bypass intended allowlist approval constraints

Also known asCVE-2026-22169

Published

Mar 3, 2026

Updated

Mar 18, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk10th percentile+0.15%

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

When sort is explicitly added to tools.exec.safeBins (non-default), the --compress-program option can invoke an external helper and bypass the intended safe-bin approval constraints in allowlist mode.

Affected Packages / Versions

Package: openclaw (npm)
Vulnerable versions: <=2026.2.21-2
Latest published npm version checked during triage: 2026.2.21-2 (as of February 22, 2026)
Patched in planned next release: 2026.2.22

Fix Commit(s)

57fbbaebca4d34d17549accf6092ae26eb7b605c

Release Process Note

patched_versions is pre-set to the planned next release (>=2026.2.22). Once that npm release is published, the advisory can be published directly.

OpenClaw thanks @tdjackey for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

When `sort` is explicitly added to `tools.exec.safeBins` (non-default), the `--compress-program` option can invoke an external helper and bypass the intended safe-bin approval constraints in allowlist mode. ## Affected Packages / Versions - Package: `openclaw` (npm) - Vulnerable versions: `<=2026.2.21-2` - Latest published npm version checked during triage: `2026.2.21-2` (as of February 22, 2026) - Patched in planned next release: `2026.2.22` ## Fix Commit(s) - `57fbbaebca4d34d17549accf6092ae26eb7b605c` ## Release Process Note `patched_versions` is pre-set to the planned next release (`>

O3 Security · Impact-Aware SCA

Is GHSA-vmqr-rc7x-3446 in your dependencies?

O3 detects GHSA-vmqr-rc7x-3446 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