CVE-2026-43575
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenClaw versions 2026.2.21 before 2026.4.10 contain an authentication bypass vulnerability in the sandbox noVNC helper route that exposes interactive browser session credentials. Attackers can access the noVNC helper route without bridge authentication to gain unauthorized access to the interactive browser session.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenClaw versions 2026.2.21 through 2026.4.9 contain an authentication bypass vulnerability in the sandbox noVNC helper route. The helper route, intended to provide interactive browser session access, fails to enforce bridge authentication, allowing unauthenticated attackers to directly access the route and obtain browser session credentials for unauthorized session access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2026.2.21, < 2026.4.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed OpenClaw versionRun the command to display the OpenClaw version (e.g., openclaw --version, or check the software's about/status page)Affected if The installed version is 2026.2.21 or later but earlier than 2026.4.10
-
Locate noVNC helper route configurationInspect the OpenClaw configuration files for settings related to noVNC, sandbox helper, or browser session access (typically in config files named openclaw.conf, sandbox.conf, or similar)Affected if The noVNC helper route is enabled in the configuration
-
Verify authentication enforcement on the noVNC routeExamine the authentication or access control settings specific to the noVNC helper endpoint; attempt an unauthenticated request to the route (e.g., accessing the noVNC helper URL directly without credentials) to confirm whether authentication is bypassedAffected if The noVNC helper route allows access without requiring bridge authentication or valid credentials
-
Check network exposure of the noVNC endpointReview network configuration, firewall rules, or reverse proxy settings to determine if the noVNC helper route is externally accessibleAffected if The noVNC helper route is exposed to untrusted networks without IP-based access restrictions
A user is affected if their OpenClaw version falls within 2026.2.21 through 2026.4.9 AND the noVNC helper route is enabled and accessible without authentication enforcement.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.4.10
Upgrade to OpenClaw version 2026.4.10 or later to obtain the patched version. If immediate upgrade is not feasible, implement network-level access controls restricting the noVNC helper route to authorized IP addresses or implement additional authentication proxying.
2026.4.10
- Identify the current OpenClaw version running in the environment
- Backup the current OpenClaw installation and configuration
- Upgrade OpenClaw to version 2026.4.10 or later by following the project's upgrade documentation
- After upgrade, verify the noVNC helper route now requires proper bridge authentication
- Test that the sandbox noVNC functionality works correctly with authentication in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-43575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-43575 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data