Summary
OpenClaw has auth inconsistency on local Browser Extension Relay /extension endpoint
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
Fix Commit(s)
7e54b6c96feb1a5c30884f2b32037b8dadd0e532
OpenClaw thanks @tdjackey for reporting.
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.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
- Require gateway-token auth on both
/extensionand/cdprelay 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.
Frequently Asked Questions
- What is GHSA-PFV7-RR5M-QMV6? GHSA-PFV7-RR5M-QMV6 is a medium-severity missing authentication for critical function vulnerability in openclaw (npm), affecting versions < 2026.2.19. It is fixed in 2026.2.19. A critical operation is accessible without requiring any authentication.
- Which versions of openclaw are affected by GHSA-PFV7-RR5M-QMV6? openclaw (npm) versions < 2026.2.19 is affected.
- Is there a fix for GHSA-PFV7-RR5M-QMV6? Yes. GHSA-PFV7-RR5M-QMV6 is fixed in 2026.2.19. Upgrade to this version or later.
- Is GHSA-PFV7-RR5M-QMV6 exploitable, and should I be worried? Whether GHSA-PFV7-RR5M-QMV6 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-PFV7-RR5M-QMV6 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-PFV7-RR5M-QMV6? Upgrade
openclawto 2026.2.19 or later.