Skip to main content
VulnerabilityPublished Updated

CVE-2026-35630: OpenClaw · QQBot native approval buttons did not enforce configured approver identity

Affects openclaw-cliSource GCVE Database

0
Compare

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

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% 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:R/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 29 Oct 2026.

What to do

Upgrade openclaw and openclaw-cli to 2026.5.18.

Affected software

ProductAffectedFixed in
npmopenclawAffected
  • <2026.5.18
Fixed in
  • 2026.5.18
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, where the issue is fixed. Until the upgrade is applied, avoid delivering native approval buttons in QQ conversations that include users who are not authorized approvers to prevent unauthorized approvals.

Description

OpenClaw CLI versions prior to 2026.5.18 have a vulnerability in the QQBot native approval buttons where the configured approver identity is not enforced. This allows any QQ user who can see an approval message to click the approval button and resolve the request, potentially executing actions without proper authorization. The issue is specific to native QQBot approval buttons and does not affect text command approvals. A fix is available in version 2026.5.18.

References

Community reviews

Loading reviews…