GitHub Advisoryadvisory · npm

GHSA-vpj2-69hf-rppw OpenClaw: Browser control startup could continue unauthenticated after auth bootstrap failure

HIGH Published 2026-03-02 Modified 2026-03-30 Official page ↗
Aliases
CVE-2026-32041
Ecosystem
npm
Packages
openclaw
Severity
High
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L
Weaknesses
CWE-306
Reviewed
2026-03-02

Affected packages

• npm openclaw: < 2026.3.1 → fixed in 2026.3.1

Description

Summary When browser control started without explicit auth credentials, OpenClaw attempted to bootstrap auth automatically. In affected versions, if that bootstrap step threw an error, startup could continue and expose browser-control routes without authentication. Impact On affected deployments, a local process (or a loopback-reachable SSRF path) could access browser-control routes, including evaluate-capable actions, without auth. Fix Startup now fails closed: if bootstrap auth fails and no explicit token/password is configured, browser-control startup aborts. Affected and Patched Versions • Affected: `<= 2026.2.26` • Patched: `2026.3.1`

Related

Alias · CVE (1)

  • CVE-2026-32041 OpenClaw versions prior to 2026.3.1 fail to properly handle authentication bootstrap errors during startup, allowing browser-control routes… vulnerability

Weakness · CWE (1)

  • CWE-306 Missing Authentication for Critical Functionality weakness

References