Skip to main content
VulnerabilityPublished Updated

CVE-2026-32021: Openclaw cli · OpenClaw has a Feishu allowFrom authorization bypass via display-name collision

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.7.1 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
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.7.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 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

A patch is available and planned for release in OpenClaw CLI version 2026.2.22. Users should upgrade to version 2026.2.22 or later to ensure that Feishu allowlist authorization correctly enforces ID-only matching and prevents display-name collision bypasses.

Description

OpenClaw CLI versions up to 2026.2.21-2 have a vulnerability in the Feishu allowlist authorization mechanism where an attacker can bypass authorization by exploiting display-name collisions. The allowlist is intended to match sender IDs, but the system incorrectly accepted mutable display names, allowing unauthorized senders to be authorized if their display name matched an allowlisted ID. This issue is fixed in version 2026.2.22 and later by enforcing strict ID-only matching and normalizing ID prefixes.

References

Community reviews

Loading reviews…