How severe is GHSA-qw99-grcx-4pvm?

GHSA-qw99-grcx-4pvm has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qw99-grcx-4pvm?

GHSA-qw99-grcx-4pvm affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-qw99-grcx-4pvm?

Update openclaw to 2026.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qw99-grcx-4pvm is resolved across your whole dependency graph.

How do I detect GHSA-qw99-grcx-4pvm 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-qw99-grcx-4pvm 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-qw99-grcx-4pvm?

O3 pinpoints whether GHSA-qw99-grcx-4pvm 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-qw99-grcx-4pvm actively exploited in the wild?

No public exploit code has been indexed for GHSA-qw99-grcx-4pvm 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-qw99-grcx-4pvm?

GHSA-qw99-grcx-4pvm has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th 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-qw99-grcx-4pvm?

GHSA-qw99-grcx-4pvm is classified as CWE-1327 (CWE-1327). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qw99-grcx-4pvm published, and has it been updated?

GHSA-qw99-grcx-4pvm was published on February 17, 2026 and was last updated on March 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-qw99-grcx-4pvm

MEDIUM

OpenClaw's Chrome extension relay binds publicly due to wildcard treated as loopback

Also known asCVE-2026-28395

Published

Feb 17, 2026

Updated

Mar 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk31th percentile+0.19%

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

Description

Summary

The Chrome extension relay (ensureChromeExtensionRelayServer) previously treated wildcard hosts (0.0.0.0 / ::) as loopback, which could make it bind the relay HTTP/WS server to all interfaces when a wildcard cdpUrl was passed.

Impact

If configured with a wildcard cdpUrl, relay HTTP endpoints could become reachable off-host, leaking service presence/port and enabling DoS/brute-force traffic against the relay token header.

Affected Packages / Versions

Package: openclaw (npm)
Affected: >= 2026.1.14-1 < 2026.2.12

Fixed Versions

Patched: >= 2026.2.12 (released 2026-02-13)

Fix Commit(s)

8d75a496bf5aaab1755c56cf48502d967c75a1d0

Notes

Earlier hardening for /json* auth and /cdp token checks landed in:
- a1e89afcc19efd641c02b24d66d689f181ae2b5c

Thanks @qi-scape for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.1.14-1&&< 2026.2.12	2026.2.12

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

Frequently Asked Questions

## Summary The Chrome extension relay (`ensureChromeExtensionRelayServer`) previously treated wildcard hosts (`0.0.0.0` / `::`) as loopback, which could make it bind the relay HTTP/WS server to all interfaces when a wildcard `cdpUrl` was passed. ## Impact If configured with a wildcard `cdpUrl`, relay HTTP endpoints could become reachable off-host, leaking service presence/port and enabling DoS/brute-force traffic against the relay token header. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `>= 2026.1.14-1 < 2026.2.12` ## Fixed Versions - Patched: `>= 2026.2.12` (re

O3 Security · Impact-Aware SCA

Is GHSA-qw99-grcx-4pvm in your dependencies?

O3 detects GHSA-qw99-grcx-4pvm 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