NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · OpenClaw

CVE-2026-32008: OpenClaw browser navigation guard allowed non-network URL schemes, enabling authenticated browser-tool users to access file:// local files

mediumCVSS 3.1 6.5GHSA-45cg-2683-gfmq

OpenClaw before 2026.2.21 let an authenticated gateway user point the browser tool at `file://` URLs and read local files through snapshot and extract actions. The navigation guard checked only http and https targets and let every other scheme through. Upgrade to openclaw 2026.2.21.

Published Mar 3, 2026 · Updated Mar 19, 2026 · Analysis Oct 31, 2026

What an attacker can do

assertBrowserNavigationAllowed() in src/browser/navigation-guard.ts ran its network and SSRF checks only for http: and https: URLs. Any other protocol returned early and was allowed. A user with gateway credentials and browser-tool access could navigate a browser session to file:///etc/passwd, then read the page through the snapshot or extract actions.

The attacker gets any file the OpenClaw process user can read. The advisory names config files and secrets in that user's context. API keys and tokens for model providers and connected channels are the likely prize.

The precondition is valid gateway authentication with the browser tool enabled. That makes this a privilege problem: a low-privilege user can read host files. It also matters when an agent drives the browser. A prompt-injected agent that can call the browser tool could be steered to a file:// URL, though the advisory describes only the authenticated-user path. The CVSS 3.1 vector rates confidentiality impact high and integrity and availability none.

Who is affected

The openclaw npm package below 2026.2.21 is affected (the advisory text says up to 2026.2.19-2). Only gateways with the browser tool enabled are exposed, and the attacker must be able to call browser actions. Check the version:

npm ls openclaw

Then confirm whether the browser tool is turned on in your gateway configuration.

openclaw

Ecosystem
npm
Affected
< 2026.2.21
Fixed in
2026.2.21
Check
npm ls openclaw

How to fix it

Upgrade to openclaw 2026.2.21.

npm install [email protected]

Fix commit 220bd95 makes the guard fail closed. Only about:blank is allowed among non-network URLs. Any other non-network scheme, including file:, data: and javascript:, throws InvalidBrowserNavigationUrlError with the text "Navigation blocked: unsupported protocol". Other about: URLs such as about:srcdoc are blocked too. The advisory gives no workaround. Until you upgrade, disable the browser tool or limit who can reach the gateway.

How to tell if you were hit

Search gateway and browser-tool logs for navigation requests whose URL starts with file:, data: or javascript:, especially file:///etc/passwd or paths to config and credential files. On patched versions, such attempts show the error "Navigation blocked: unsupported protocol". Follow-up snapshot or extract calls on those sessions show what was read. If an agent uses the browser tool, Beam records agent file access and MCP tool calls, which can show reads of sensitive files.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Impact

assertBrowserNavigationAllowed() validated only http:/https: network targets but implicitly allowed other schemes. An authenticated gateway user could navigate browser sessions to file:// URLs and read local files via browser snapshot/extraction flows.

Affected Component

  • src/browser/navigation-guard.ts

Technical Reproduction

  1. Authenticate to a gateway that has browser tooling enabled.
  2. Invoke browser navigation with a file:// URL (for example file:///etc/passwd).
  3. Read page content through browser snapshot/extract actions.

Demonstrated Impact

An attacker with valid gateway credentials and browser-tool access can exfiltrate local files readable by the OpenClaw process user (for example config/secrets in that user context).

Environment

  • OpenClaw browser tool enabled
  • Attacker has authenticated access capable of invoking browser actions

Remediation Advice

Reject unsupported navigation schemes and allow only explicitly safe non-network URLs. OpenClaw now blocks non-network schemes (such as file:, data:, and javascript:) while preserving about:blank.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected versions: <= 2026.2.19-2
  • Patched in planned next release: 2026.2.21

Fix Commit(s)

  • 220bd95eff6838234e8b4b711f86d4565e16e401

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.21) so once npm 2026.2.21 is published, the advisory can be published directly.

OpenClaw thanks @q1uf3ng for reporting.

Credited to q1uf3ng.

Questions

Does the attacker need to be logged in?

Yes. The attacker needs valid gateway credentials and access to the browser tool. The CVSS vector lists low privileges required and no user interaction.

What can be read?

Any file readable by the OpenClaw process user, for example configuration and secrets. The advisory gives file:///etc/passwd as the test case.

Does the fix block all non-web URLs?

Almost all. It allows http:, https: (with the existing checks) and about:blank. It blocks everything else, including file:, data: and javascript:.

Is CVE-2026-32008 exploited in the wild?

No source reports exploitation, and the entry is not in CISA's KEV catalog.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More OpenClaw vulnerabilities

All OpenClaw entries