Skip to main content
VulnerabilityPublished Updated

CVE-2026-53821: OpenClaw · Trusted-proxy Control UI WebSocket accepted client-declared scopes before pairing

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2026.5.18 soon.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.5.18
CVSS:3.1/AV:N/AC:L/PR:L/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 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.5.18.

Affected software

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

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.5.18 or later, which contains the official fix for this vulnerability. Prior to upgrading, restrict trusted-proxy Control UI access to only those users who require the scopes they request. Additionally, restart the gateway after modifying trusted-proxy authorization policies to ensure changes take effect.

Description

OpenClaw CLI versions from 2026.1.29 up to but not including 2026.5.18 have a vulnerability in trusted-proxy Control UI mode where WebSocket clients could declare operator scopes before these were properly authorized. This allows an unpaired or restricted trusted-proxy client to gain operator.admin privileges on a live WebSocket connection, enabling admin-level Gateway RPCs until the connection ends or is revalidated. The issue does not affect shared-secret Control UI sessions. A fix is available in version 2026.5.18.

References

Community reviews

Loading reviews…