/

CVE-2026-32972

Severity:

HIGH RISK

(7.1)

Authorization Bypass in OpenClaw Browser Profile Management

CVE-2026-32972

Analyzed

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-863

Impact:

Privilege Escalation and Unauthorized Configuration Manipulation

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

OpenClaw contains an authorization bypass that lets users with only operator.write permissions invoke admin-only browser profile management routes via browser.request.

Under certain conditions, an authenticated operator can create or modify browser profiles and persist attacker-controlled remote CDP endpoints to disk without possessing operator.admin privileges.

Affected context

The vulnerability appears in OpenClaw deployments where:

  • Role-based permissions differentiate between operator.write and operator.admin.
  • Browser profile management is intended to be restricted to admin-only routes.
  • The browser.request mechanism can be used by non-admin operators as part of normal workflow.

In this context, insufficient enforcement of authorization on specific profile management routes allows lower-privileged operators to perform admin-only actions related to browser profiles and remote CDP endpoints.

Exploit preconditions

  • Attack surface: Application control plane / management API, specifically the browser.request functionality.
  • Required access: Valid authenticated account with at least operator.write permission (but lacking operator.admin).
  • Trigger point: Issuing crafted browser.request calls that target admin-only browser profile management routes.
  • Why exploitation is possible: The authorization layer does not correctly enforce or re-check the required privilege level on these routes when accessed through browser.request, allowing privilege boundaries between operator and admin roles to be bypassed.

Why this happens

This issue is rooted in improper authorization checks on sensitive operations, aligning with CWE-863: Incorrect Authorization.

The system assumes that only admin users will reach certain browser profile management routes, but the browser.request mechanism exposes those routes to users with lesser permissions without enforcing the intended operator.admin requirement.

In abstract terms, a privileged operation (persistent modification of browser profiles and remote CDP endpoints) is bound to an access path that does not validate the caller's effective role, causing a mismatch between the security policy (admin-only) and the actual authorization logic.

Potential impact

  • Non-admin operators could create or modify browser profiles beyond their intended permissions.
  • Attackers may persist malicious or untrusted remote CDP endpoints to disk.
  • Compromised profiles could be used to route browser automation or sessions through attacker-controlled infrastructure.
  • Unauthorized configuration changes can weaken monitoring, forensics, or isolation assumptions around browser sessions.
  • Privilege escalation in practice, as users with operator.write gain access to admin-grade configuration actions.

General mitigation guidance

Effective mitigation focuses on enforcing consistent, centralized authorization checks around sensitive profile-management paths:

  • Ensure every browser profile management route explicitly validates that the caller holds the intended admin-equivalent privilege before executing.
  • Treat generic request dispatchers (such as browser.request) as untrusted entry points that must not bypass route-level authorization policies.
  • Apply a least-privilege permissions model so that non-admin roles cannot modify shared or persistent browser configuration, especially remote CDP endpoints.
  • Introduce defense-in-depth checks (e.g., at the service boundary and inside business logic) to verify that only appropriately privileged roles can alter persisted profiles.
  • Favor "secure by default" designs where new routes are denied for all roles until explicitly granted.

How teams detect issues like this

Detection generally revolves around reviewing authorization logic and monitoring for anomalous configuration changes:

  • Use static analysis or code search to identify routes and handlers that perform browser profile changes but lack explicit role checks or rely solely on client-side indicators.
  • During code review, treat any mechanism that forwards or proxies requests (browser.request-like APIs) as high-risk and verify that downstream handlers still enforce role-based access.
  • Implement logging and auditing on all profile creation/modification operations, including recording the caller's role and origin, to detect non-admin users performing admin-level actions.
  • Enforce security policies in CI/CD (e.g., lint rules or policy-as-code) that require explicit authorization annotations on sensitive operations.
  • Periodically run authorization tests or security regression suites that attempt admin-only operations from lower-privilege roles to validate controls.

Sources

SourceLink
github.comgithub.com/openclaw/openclaw/security/advisories/GHSA-vmhq-cqm9-6p7q
vulncheck.comvulncheck.com/advisories/openclaw-authorization-bypass-in-browser-profile-management-via-browser-request

Frequently asked

questions

It is exploitable through the OpenClaw control interface by any authenticated user who can reach the browser.request functionality with operator.write permissions, subject to network exposure and authentication controls.

Yes. The attacker must have a valid account with at least operator.write permission. However, they do not need operator.admin, which is the intended requirement for these actions.

The safest pattern is to enforce strict, server-side authorization on all browser profile management routes, ensuring they explicitly require admin-level privileges regardless of how they are invoked (directly or via browser.request), and to centralize RBAC checks in shared middleware or policy layers.

Adopt a uniform access-control design where every sensitive operation includes explicit role checks, treat any generic dispatch or proxy mechanism as untrusted until proven safe, and incorporate automated tests and reviews that validate that lower-privileged roles cannot invoke admin-only operations via alternate paths.

Find out what's already
exploitable in your codebase.