How severe is GHSA-g55j-c2v4-pjcg?

GHSA-g55j-c2v4-pjcg has a CVSS score of 8.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-g55j-c2v4-pjcg?

GHSA-g55j-c2v4-pjcg affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-g55j-c2v4-pjcg?

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

How do I detect GHSA-g55j-c2v4-pjcg 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-g55j-c2v4-pjcg 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-g55j-c2v4-pjcg?

O3 pinpoints whether GHSA-g55j-c2v4-pjcg 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-g55j-c2v4-pjcg actively exploited in the wild?

No public exploit code has been indexed for GHSA-g55j-c2v4-pjcg 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-g55j-c2v4-pjcg?

GHSA-g55j-c2v4-pjcg has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th 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-g55j-c2v4-pjcg?

GHSA-g55j-c2v4-pjcg is classified as OS Command Injection (CWE-78), Missing Authentication (CWE-306). These weakness types 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-g55j-c2v4-pjcg published, and has it been updated?

GHSA-g55j-c2v4-pjcg was published on February 4, 2026 and was last updated on February 6, 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-g55j-c2v4-pjcg

HIGH

OpenClaw vulnerable to Unauthenticated Local RCE via WebSocket config.apply

Also known asCVE-2026-25593

Published

Feb 4, 2026

Updated

Feb 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk46th percentile+0.61%

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.4Mdownloads / week

Description

Summary

An unauthenticated local client could use the Gateway WebSocket API to write config via config.apply and set unsafe cliPath values that were later used for command discovery, enabling command injection as the gateway user.

Impact

A local process on the same machine could execute arbitrary commands as the gateway process user.

Details

config.apply accepted raw JSON and wrote it to disk after schema validation.
cliPath values were not constrained to safe executable names/paths.
Command discovery used a shell invocation when resolving executables.

Mitigation

Upgrade to a patched release. If projects cannot upgrade immediately, set gateway.auth and avoid custom cliPath values.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

### Summary An unauthenticated local client could use the Gateway WebSocket API to write config via `config.apply` and set unsafe `cliPath` values that were later used for command discovery, enabling command injection as the gateway user. ### Impact A local process on the same machine could execute arbitrary commands as the gateway process user. ### Details - `config.apply` accepted raw JSON and wrote it to disk after schema validation. - `cliPath` values were not constrained to safe executable names/paths. - Command discovery used a shell invocation when resolving executables. ### Mitig

O3 Security · Impact-Aware SCA

Is GHSA-g55j-c2v4-pjcg in your dependencies?

O3 detects GHSA-g55j-c2v4-pjcg 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