Skip to main content
CVE-2026-28472VulnerabilityPublished Updated

Openclaw cli: OpenClaw's gateway connect could skip device identity checks when auth.token was present but not yet

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2026.7.1 as a priority.

Data as of 17 Nov 2026, 20:25 UTC

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

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 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.7.1.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • <2026.7.1
Fixed in
  • 2026.7.1

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

AI-suggested

Upgrade OpenClaw CLI to version 2026.2.2 or later, where the vulnerability is fixed. Additionally, restrict gateway WebSocket access to trusted networks and users, for example by limiting Tailnet users and ACLs when using Tailscale Serve, to reduce exposure to untrusted parties.

Description

OpenClaw CLI versions up to 2026.2.1 have a vulnerability in the gateway WebSocket connect handshake that allows skipping device identity checks if an auth.token is present but not validated. This could enable unauthorized clients to connect without proper device identity or pairing, potentially granting operator access depending on configuration. The issue is fixed in version 2026.2.2 by requiring validated shared-secret authentication for skipping device identity. The gateway should be restricted to trusted networks and users to mitigate risk.

References

Community reviews

Loading reviews…