Skip to main content
VulnerabilityPublished Updated

CVE-2026-53827: OpenClaw · message.action forwarding could send Gateway credentials to model-supplied loopback URLs

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 2026.5.2 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.5.2
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.5.2.

Affected software

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

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 in version 2026.5.2. Until patched, restrict message action forwarding and avoid using model-supplied loopback targets. Additionally, narrow channel and tool allowlists, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when not needed.

Description

OpenClaw CLI versions from 2026.1.29 up to but not including 2026.5.2 have a vulnerability where message.action forwarding can send Gateway credentials to model-supplied loopback URLs. This occurs when model-controlled action metadata selects a loopback Gateway URL, potentially exposing tokens and action payloads to a local listener. The vulnerability depends on the operator's configuration and whether untrusted input can reach this path. A patch is available in version 2026.5.2. Mitigations include restricting message action forwarding, avoiding model-supplied loopback targets until patched, and narrowing allowlists.

References

Community reviews

Loading reviews…