How severe is GHSA-jmmg-jqc7-5qf4?

GHSA-jmmg-jqc7-5qf4 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jmmg-jqc7-5qf4?

GHSA-jmmg-jqc7-5qf4 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-jmmg-jqc7-5qf4?

Update openclaw to 2026.2.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmmg-jqc7-5qf4 is resolved across your whole dependency graph.

How do I detect GHSA-jmmg-jqc7-5qf4 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-jmmg-jqc7-5qf4 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-jmmg-jqc7-5qf4?

O3 pinpoints whether GHSA-jmmg-jqc7-5qf4 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-jmmg-jqc7-5qf4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jmmg-jqc7-5qf4 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-jmmg-jqc7-5qf4?

GHSA-jmmg-jqc7-5qf4 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th 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-jmmg-jqc7-5qf4?

GHSA-jmmg-jqc7-5qf4 is classified as CWE-307 (CWE-307). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jmmg-jqc7-5qf4 published, and has it been updated?

GHSA-jmmg-jqc7-5qf4 was published on March 3, 2026 and was last updated on March 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.

GHSA-jmmg-jqc7-5qf4: openclaw Remote Code Execution (High 7.5)

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk21th percentile+0.18%

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

This issue is a browser-origin WebSocket auth chain on local loopback deployments using password auth. It is serious, but conditional: an attacker must get the user to open a malicious page and then successfully guess the gateway password.

Context and Preconditions

OpenClaw’s web/gateway surface is designed for local use and trusted-operator workflows. In affected versions, a browser-origin client could combine three behaviors:

Origin checks not enforced for some non-Control-UI WebSocket client IDs.
Loopback auth attempts exempt from password-failure throttling.
Silent local pairing path available to browser-origin non-Control-UI clients.

Successful exploitation requires all of the following:

Gateway reachable on loopback (default).
Password auth mode in use.
Victim opens attacker-controlled web content.
Password is guessable within feasible brute-force/dictionary attempts.

Practical Impact

If the password is guessed, an attacker can establish an authenticated operator WebSocket session and invoke control-plane methods available to that role. This is not an unauthenticated internet-exposed RCE class issue by itself; it is a local browser-origin auth-hardening gap with meaningful impact under the conditions above.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <=2026.2.24 (latest published npm version as of February 26, 2026)
Patched versions : >=2026.2.25

Fix Commit(s)

c736f11a16d6bc27ea62a0fe40fffae4cb071fdb

Fix Details

Enforce browser-origin checks for direct browser WebSocket clients beyond Control UI/Webchat (trusted-proxy forwarded flows remain supported).
Apply browser-origin auth failure throttling with loopback exemption disabled.
Block silent auto-pairing for non-Control-UI browser-origin clients.

Release Process Note

patched_versions is pre-set to the planned next npm release (2026.2.25) so once that release is published, the advisory is published.

OpenClaw thanks @luz-oasis for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

This issue is a browser-origin WebSocket auth chain on local loopback deployments using password auth. It is serious, but conditional: an attacker must get the user to open a malicious page and then successfully guess the gateway password. ## Context and Preconditions OpenClaw’s web/gateway surface is designed for local use and trusted-operator workflows. In affected versions, a browser-origin client could combine three behaviors: - Origin checks not enforced for some non-Control-UI WebSocket client IDs. - Loopback auth attempts exempt from password-failure throttling. - Silent local pairin

O3 Security · Impact-Aware SCA

Is GHSA-jmmg-jqc7-5qf4 in your dependencies?

O3 detects GHSA-jmmg-jqc7-5qf4 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

GHSA-jmmg-jqc7-5qf4