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.
openclaw (npm)< 2026.3.23>= 2026.3.23v2026.3.23-2 (630f1479c44f78484dfa21bb407cbe6f171dac87)2026.3.23-2The 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.
d5dc6b6573ae489bc7e5651090f4767b93537c9e — fix(gateway): require auth for canvas routesThe 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.
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.
{
"github_reviewed": true,
"github_reviewed_at": "2026-03-26T18:59:00Z",
"cwe_ids": [
"CWE-287"
],
"severity": "MODERATE",
"nvd_published_at": null
}