Skip to main content
VulnerabilityPublished Updated

CVE-2026-53859: OpenClaw · Hostname checks could treat trailing-dot hosts inconsistently

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.5.28 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.5.28
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.5.28.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.5.28
Fixed in
  • 2026.5.28

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available starting with OpenClaw CLI version 2026.5.26. Until systems are updated, operators should block private-network and metadata destinations at the proxy or network layer. Additionally, operators should keep channel and tool allowlists narrow, avoid sharing a Gateway between mutually untrusted users, and disable the affected feature when it is not needed.

Description

OpenClaw CLI versions from 2026.1.29 up to but not including 2026.5.28 have a vulnerability where hostname checks treat trailing-dot hosts inconsistently. This can allow requests with trailing-dot hostnames to bypass blocklist comparisons, potentially reaching destinations that operators intended to block. The vulnerability affects features that accept model- or workspace-derived URLs and depends on operator configuration and input trust levels. A patch is available starting with version 2026.5.26. Until patched, network-level blocking of private-network and metadata destinations is recommended, along with minimizing allowlists and disabling the affected feature if not needed.

References

Community reviews

Loading reviews…