dbcve.org
OpenclawApplication

CVE-2026-53839

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-12
Fix available
A fix is available. Upgrade to 2026.5.7 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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.5.7 contains a hostname validation vulnerability in retry endpoint checks that allows matching hostname prefixes instead of exact hostnames. Attackers can exploit this by crafting a hostname prefix resembling a trusted host to send authentication material to untrusted endpoints.

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 · moderate confidence

OpenClaw before version 2026.5.7 has a hostname validation flaw in its retry endpoint logic. The application uses prefix matching for hostnames rather than exact matching, allowing an attacker to register a hostname like 'trustedexample.com.evil.com' which would match against 'trustedexample.com' in the allowlist. This causes authentication credentials to be sent to attacker-controlled servers.

MitigationUpgrade to OpenClaw 2026.5.7 or later. If immediate patching is not possible, implement exact hostname matching with proper validation (no prefix/substring matching) in the retry endpoint checks.

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.5.7

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check installed OpenClaw version
    Run the command to display the OpenClaw version (e.g., openclaw --version, openclaw -v, or check package manager listing)
    Affected if The installed version is earlier than 2026.5.7 (e.g., 2026.5.6, 2026.4.0, etc.)
  2. Identify if retry endpoint is configured
    Review OpenClaw configuration files or running service settings to determine if the retry endpoint feature is enabled
    Affected if The retry endpoint is active and accessible in the environment
  3. Examine hostname whitelist configuration
    Inspect the hostname validation settings in OpenClaw config files, looking for entries in the trusted hosts or allowed domains list
    Affected if Any hostname entries use prefix-style matching or allow substring matches (e.g., 'trusted-host' matching 'trusted-host.attacker.com')
  4. Audit registered hostnames for prefix patterns
    Query the system for registered hostnames or callback URLs, searching for patterns where an attacker-controlled domain starts with a legitimate trusted hostname
    Affected if There are registered hostnames that appear to be prefixes of other trusted hostnames (e.g., 'trusted-host.attacker.com' alongside 'trusted-host')

You are affected if OpenClaw version is below 2026.5.7 AND the retry endpoint is enabled with hostname validation using prefix matching rather than exact matching.

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.5.7 or later
Fixed in 2026.5.7
Interim mitigation

Upgrade to OpenClaw 2026.5.7 or later. If immediate patching is not possible, implement exact hostname matching with proper validation (no prefix/substring matching) in the retry endpoint checks.

Recommended fix Moderate confidence

2026.5.7

  1. 1. Back up your current OpenClaw installation and configuration files.
  2. 2. Download OpenClaw version 2026.5.7 or later from the official source.
  3. 3. Stop the OpenClaw service.
  4. 4. Replace the existing OpenClaw files with the new version.
  5. 5. Verify the hostname validation now performs exact matching rather than prefix matching in retry endpoint checks.
  6. 6. Restart the OpenClaw service.
  7. 7. Test that authentication materials are only sent to exact hostname matches, not prefixes.

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53839 — 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-53839 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