Skip to main content
VulnerabilityPublished Updated

CVE-2026-35670: OpenClaw · Synology Chat reply delivery could be rebound through username-based user resolution

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 2026.3.24 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.24
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/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.3.24.

Affected software

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

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

AI-suggested

A fix is available and was shipped in OpenClaw CLI version 2026.3.22 and later. Users should upgrade to version 2026.3.22 or newer to mitigate this issue. The fix ensures replies are bound to the stable webhook user identifier by default, with username rebinding requiring explicit opt-in.

Description

A vulnerability in the OpenClaw CLI's Synology Chat integration allows reply delivery to be rebound through username-based user resolution instead of the stable numeric user_id. This issue affects versions prior to 2026.3.22 and was fixed in version 2026.3.22. The fix ensures replies remain bound to the stable webhook user identifier unless an explicit opt-in for username rebinding is enabled.

References

Community reviews

Loading reviews…