Imagine someone silently watching everything you do in your browser — every login, every form, every click — without ever needing a password. That's exactly what this flaw makes possible.
Who's Affected and Why It Matters
If your organization runs OpenClaw versions 2026.2.21 through 2026.4.9 — on any operating system — you are exposed. OpenClaw is used to spin up sandboxed, interactive browser environments, the kind of infrastructure increasingly common in enterprise security tools, automated testing pipelines, and cloud-based browser isolation platforms. Because it runs cross-platform, the blast radius spans Windows, Linux, and macOS deployments alike.
This isn't a theoretical risk buried in some edge-case configuration. The vulnerability sits in a core part of how OpenClaw handles remote browser access. Security teams managing shared infrastructure, DevSecOps pipelines, or any customer-facing browser sandbox should treat this as high priority. The CVSS score — 9.8 out of 10 — puts it firmly in the "drop everything and patch" category.
What an Attacker Can Actually Do
Here's the scenario in plain terms. OpenClaw lets users interact with a live browser running inside a protected environment — think of it like a remote-controlled browser locked behind a gate. The "gate" is supposed to require authentication: prove who you are before you get access. This vulnerability means the gate has a side door that was left wide open.
An attacker who knows what they're looking for — and the details are now public — can walk through that side door and land directly inside the interactive browser session. From there, they can see everything the session contains: active login tokens, session cookies, credentials typed into forms, sensitive documents being viewed. In a worst-case scenario involving a shared or multi-tenant platform, one attacker could access sessions belonging to multiple users simultaneously.
What makes this especially dangerous is that the attacker doesn't need to be sophisticated or patient. There's no need to crack a password, social-engineer an employee, or wait for a user to make a mistake. The path in is direct, requires no credentials, and leaves the victim with no obvious indication anything went wrong. Silent, fast, and potentially devastating for organizations handling sensitive data through sandboxed browsers.
The Technical Detail That Security Researchers Need to Know
The vulnerability resides specifically in the noVNC helper route within OpenClaw's sandbox component. noVNC is a browser-based VNC client — it's the technology that renders the interactive browser session visually in real time. The helper route, which is designed to facilitate that connection, fails to enforce bridge authentication before granting access. This is a classic authentication bypass vulnerability (CWE-306: Missing Authentication for Critical Function), and it directly exposes the session credential material that noVNC uses to establish and maintain those live interactive connections. Tracked as CVE-2026-43575, it carries a CVSS v3.1 base score of 9.8 (CRITICAL).
Real-World Context: Discovered, Not Yet Exploited
As of publication, there is no confirmed active exploitation of CVE-2026-43575 in the wild. No threat actor campaigns, no known victim organizations, and no proof-of-concept exploit code has been publicly attributed to malicious use — yet. That window of safety is narrow and historically short once a critical authentication bypass with a near-perfect CVSS score becomes public knowledge.
The vulnerability was identified and responsibly disclosed ahead of the patched release. The OpenClaw project has issued a fix in version 2026.4.10. Security teams should not wait for exploitation to be confirmed before acting — by that point, the damage is already done.
What You Should Do Right Now
- Update to OpenClaw 2026.4.10 immediately. This is the patched release. Any instance running versions 2026.2.21 through 2026.4.9 is vulnerable. Check every environment — development, staging, and production — since sandbox tooling often runs in non-production systems that get overlooked during patch cycles.
- Audit your noVNC-exposed endpoints now. Before or while patching, review your network configuration to confirm whether your OpenClaw noVNC helper route is exposed to untrusted networks or the public internet. If it is, restrict access via firewall rules or VPN requirements as an immediate interim control until the patch is applied.
- Rotate any credentials or session tokens handled in OpenClaw browser sessions since 2026.2.21. If your sandboxed browser environment has been used to access authenticated services, internal tools, or sensitive data, assume those sessions may have been observed. Invalidate active tokens, rotate API keys, and force re-authentication for any accounts accessed through the affected infrastructure.
CVE: CVE-2026-43575 | CVSS: 9.8 Critical | Affected versions: OpenClaw 2026.2.21 – 2026.4.9 | Fixed in: OpenClaw 2026.4.10 | Platforms: Cross-platform