Disclosed weakness · no CVE recorded

OpenClaw’s Chrome MCP session could bypass its strict navigation policy

OpenClaw · OpenClaw browser integration for existing Chrome MCP sessions

First documented disclosure · Review checkpoint

Summary

An existing Chrome session could follow a navigation whose redirects OpenClaw could not inspect under its strict private-network policy.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The project documented the defect and its repair. The reviewed sources identify no malicious use.

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The existing-session transport could forward navigation without enforcing policy throughout the redirect chain.

Conditions required

An existing-session Chrome MCP profile is used with private-network navigation explicitly forbidden.

Potential impact

A browser could reach a destination outside its permitted network boundary. No data exposure was established.

Affected versions and configurations

The project has not published a complete affected version range.

Fix and mitigation status

OpenClaw 2026.11.2 includes the fix. The exact first fixed release across all release lines is unverified.

Practical next steps

Update OpenClaw. Use a browser profile that can inspect redirects when strict network isolation is required.

Operating lesson

Reject navigation when the browser transport cannot enforce the configured destination policy.

Evidence and limits

The documented fix refuses web navigation and tab opens on this transport in strict mode. The project distinguishes this case from profiles capable of enforcing that policy.

Sources