How severe is GHSA-pfv7-rr5m-qmv6?

No CVSS score has been assigned to GHSA-pfv7-rr5m-qmv6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pfv7-rr5m-qmv6?

GHSA-pfv7-rr5m-qmv6 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-pfv7-rr5m-qmv6?

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

How do I detect GHSA-pfv7-rr5m-qmv6 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-pfv7-rr5m-qmv6 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-pfv7-rr5m-qmv6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pfv7-rr5m-qmv6 can be triaged on real exposure rather than presence alone.

Is GHSA-pfv7-rr5m-qmv6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pfv7-rr5m-qmv6 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-pfv7-rr5m-qmv6 published, and has it been updated?

GHSA-pfv7-rr5m-qmv6 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-pfv7-rr5m-qmv6 — openclaw

Fix: openclaw/openclaw@7e54b6c

GHSA-pfv7-rr5m-qmv6 is a security vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint

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

2.5Mdownloads / week

Description

Summary

When the optional Chrome extension relay is enabled, /extension accepted unauthenticated WebSocket upgrades while /json/* and /cdp required auth.

Affected Packages / Versions

Package: openclaw (npm)
Affected: <= 2026.2.17
Latest published npm version at triage time: 2026.2.17

Impact

This is a local-only issue on loopback (127.0.0.1) and only applies when the extension relay feature is in use. A local process on the same machine could connect to /extension without the token and interfere with extension-relay behavior.

No remote network exploit path is involved.

Fix

Require gateway-token auth on both /extension and /cdp relay WebSocket endpoints.
Keep loopback/origin checks as defense-in-depth, not as authentication.
Use one token path in setup: gateway.auth.token / OPENCLAW_GATEWAY_TOKEN.

Fix Commit(s)

7e54b6c96feb1a5c30884f2b32037b8dadd0e532

OpenClaw thanks @tdjackey 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-pfv7-rr5m-qmv6 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-pfv7-rr5m-qmv6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pfv7-rr5m-qmv6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary When the optional Chrome extension relay is enabled, `/extension` accepted unauthenticated WebSocket upgrades while `/json/*` and `/cdp` required auth. ### Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `<= 2026.2.17` - Latest published npm version at triage time: `2026.2.17` ### Impact This is a local-only issue on loopback (`127.0.0.1`) and only applies when the extension relay feature is in use. A local process on the same machine could connect to `/extension` without the token and interfere with extension-relay behavior. No remote network exploit pat

O3 Security · Impact-Aware SCA

Is GHSA-pfv7-rr5m-qmv6 in your dependencies?

O3 Security finds GHSA-pfv7-rr5m-qmv6 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