Quick answers
- Is CVE-2026-43575 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-43575 being exploited in the wild.
- How severe is CVE-2026-43575?
- Critical severity, with a CVSS score of 9.8, published 6 May 2026.
- Which products and versions are affected?
- Openclaw >= 2026.2.21 < 2026.4.10.
- Is there a fix for CVE-2026-43575?
- A patch was published on 2026-04-10: Fix merged in PR #63882; version 2026.4.10 and later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-43575 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-43575?
- Check whether you run Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass (CWE-306) in the sandbox noVNC helper route handler. The route was not properly gated behind bridge authentication middleware, allowing unauthenticated network requests to reach the interactive browser session surface. The fix gates the helper route behind bridge authentication and ensures the authentication middleware is invoked before route registration to prevent future ordering bypass. No user interaction or special preconditions are required—the helper route is network-reachable without authentication. An attacker can gain access to interactive browser session credentials or surfaces. The fix was merged in PR #63882 and released in version 2026.4.10 and later.
Affected products
- OpenClaw openclaw >= 2026.2.21 < 2026.4.10
Identifiers
- CVE-2026-43575
- GHSA-92jp-89mq-4374
Timeline
- 2026-04-17: disclosed
- 2026-04-10: patched: Fix merged in PR #63882; version 2026.4.10 and later