dbcve.org
OpenclawApplication

CVE-2026-41342

HIGH · 8.1 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 2026.3.28 or later.
See remediation →
86/100
Remediation priority · High
No privileges Zero-click

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 · unedited
OpenClaw before 2026.3.28 contains an authentication bypass vulnerability in the remote onboarding component that persists unauthenticated discovery endpoints without explicit trust confirmation. Attackers can spoof discovery endpoints to redirect onboarding toward malicious gateways and capture gateway credentials or traffic.

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 confidence

OpenClaw before version 2026.3.28 has an authentication bypass in its remote onboarding component. The discovery endpoints remain unauthenticated without requiring explicit trust confirmation, allowing attackers to spoof these endpoints and redirect the onboarding flow toward malicious gateways to capture credentials or intercept traffic.

MitigationUpgrade to OpenClaw 2026.3.28 or later. Additionally, implement explicit trust confirmation requirements for discovery endpoints in the onboarding component.

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
OpenclawApplication
Affected:< 2026.3.28

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenClaw installation version
    Check the installed OpenClaw version using the package manager, application binary, or configuration file (commonly found in /opt/openclaw/, /etc/openclaw/, or via 'openclaw --version' command)
    Affected if The installed version is lower than 2026.3.28
  2. Determine if remote onboarding component is enabled
    Inspect the OpenClaw configuration file (typically openclaw.conf or similar in /etc/openclaw/) for the 'onboarding', 'remote_onboarding', or 'discovery' module settings and verify if it is set to enabled
    Affected if Remote onboarding component is enabled and version is below 2026.3.28
  3. Verify discovery endpoint authentication status
    Send an HTTP request to the discovery endpoint (commonly /onboarding/discover, /api/discovery, or /remote/discover as defined in your OpenClaw installation) without providing any authentication credentials and observe the response
    Affected if The endpoint returns valid discovery data or accepts the request without requiring authentication or trust confirmation
  4. Check if explicit trust confirmation is required
    Review the onboarding configuration or perform a test onboarding flow to observe whether the discovery phase prompts for explicit user trust confirmation before proceeding
    Affected if No explicit trust confirmation prompt appears during the onboarding flow and the version is vulnerable

You are affected if OpenClaw version is below 2026.3.28 and the remote onboarding component with unauthenticated discovery endpoints is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.3.28 or later
Fixed in 2026.3.28
Interim mitigation

Upgrade to OpenClaw 2026.3.28 or later. Additionally, implement explicit trust confirmation requirements for discovery endpoints in the onboarding component.

Recommended fix Moderate confidence

2026.3.28

  1. 1. Verify current OpenClaw installation version using system inventory or package manager
  2. 2. If version is below 2026.3.28, schedule maintenance window for upgrade
  3. 3. Download OpenClaw version 2026.3.28 or later from the official repository (github.com)
  4. 4. Backup current configuration and database before upgrading
  5. 5. Apply upgrade following standard OpenClaw upgrade procedures
  6. 6. Verify authentication bypass is remediated by testing remote onboarding component
  7. 7. Confirm discovery endpoints now require proper authentication and trust confirmation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41342 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41342 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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