What is GHSA-6mqc-jqh6-x8fc?

## Summary Before `v2026.3.23`, Canvas and A2UI loopback requests could bypass Canvas bearer-or-capability authentication because `authorizeCanvasRequest(...)` treated `isLocalDirectRequest(...)` as an unconditional allow path. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: ` = 2026.3.23` - Latest released tag checked: `v2026.3.23-2` (`630f1479c44f78484dfa21bb407cbe6f171dac87`) - Latest published npm version checked: `2026.3.23-2` ## Root Cause The vulnerable logic lived in `src/gateway/server/http-auth.ts`. `authorizeCanvasRequest(...)` return

How severe is GHSA-6mqc-jqh6-x8fc?

No CVSS score has been assigned to GHSA-6mqc-jqh6-x8fc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6mqc-jqh6-x8fc?

GHSA-6mqc-jqh6-x8fc affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-6mqc-jqh6-x8fc?

Update openclaw to 2026.3.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6mqc-jqh6-x8fc is resolved across your whole dependency graph.

How do I detect GHSA-6mqc-jqh6-x8fc 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-6mqc-jqh6-x8fc 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-6mqc-jqh6-x8fc?

O3 pinpoints whether GHSA-6mqc-jqh6-x8fc 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-6mqc-jqh6-x8fc actively exploited in the wild?

No public exploit code has been indexed for GHSA-6mqc-jqh6-x8fc 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 type of vulnerability is GHSA-6mqc-jqh6-x8fc?

GHSA-6mqc-jqh6-x8fc is classified as CWE-288 (CWE-288). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6mqc-jqh6-x8fc published, and has it been updated?

GHSA-6mqc-jqh6-x8fc was published on March 26, 2026 and was last updated on April 10, 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-6mqc-jqh6-x8fc

Fix: openclaw/openclaw@630f147

GHSA-6mqc-jqh6-x8fc is a CWE-288 vulnerability in openclaw. O3 Security confirms whether GHSA-6mqc-jqh6-x8fc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Gateway Canvas local-direct requests bypass Canvas HTTP and WebSocket authentication

Also known asCVE-2026-35634

Published

Mar 26, 2026

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.1Mdownloads / week

Description

Summary

Before v2026.3.23, Canvas and A2UI loopback requests could bypass Canvas bearer-or-capability authentication because authorizeCanvasRequest(...) treated isLocalDirectRequest(...) as an unconditional allow path.

Affected Packages / Versions

Package: openclaw (npm)
Affected: < 2026.3.23
Fixed: >= 2026.3.23
Latest released tag checked: v2026.3.23-2 (630f1479c44f78484dfa21bb407cbe6f171dac87)
Latest published npm version checked: 2026.3.23-2

Root Cause

The vulnerable logic lived in src/gateway/server/http-auth.ts. authorizeCanvasRequest(...) returned { ok: true } for local-direct requests before checking bearer authentication or an active node canvas capability, which meant unauthenticated loopback Canvas HTTP and WebSocket requests could succeed.

Fix Commit(s)

d5dc6b6573ae489bc7e5651090f4767b93537c9e — fix(gateway): require auth for canvas routes

Release Status

The fix commit is contained in released tags v2026.3.23 and v2026.3.23-2. The latest shipped tag and npm release both include the fix.

Code-Level Confirmation

src/gateway/server/http-auth.ts no longer contains the local-direct early return in authorizeCanvasRequest(...).
src/gateway/server.canvas-auth.test.ts adds the regression test denies canvas HTTP/WS on loopback without bearer or capability by default.

Thanks @smaeljaish771 for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Summary Before `v2026.3.23`, Canvas and A2UI loopback requests could bypass Canvas bearer-or-capability authentication because `authorizeCanvasRequest(...)` treated `isLocalDirectRequest(...)` as an unconditional allow path. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `< 2026.3.23` - Fixed: `>= 2026.3.23` - Latest released tag checked: `v2026.3.23-2` (`630f1479c44f78484dfa21bb407cbe6f171dac87`) - Latest published npm version checked: `2026.3.23-2` ## Root Cause The vulnerable logic lived in `src/gateway/server/http-auth.ts`. `authorizeCanvasRequest(...)` return

O3 Security · Impact-Aware SCA

Is GHSA-6mqc-jqh6-x8fc in your dependencies?

O3 detects GHSA-6mqc-jqh6-x8fc 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