GitHub Advisoryadvisory · npm

GHSA-j4xf-96qf-rx69 OpenClaw has a Feishu allowFrom authorization bypass via display-name collision

MEDIUM Published 2026-03-03 Modified 2026-03-30 Official page ↗
Aliases
CVE-2026-32021
Ecosystem
npm
Packages
openclaw
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weaknesses
CWE-639, CWE-863
Reviewed
2026-03-03

Affected packages

• npm openclaw: < 2026.2.22 → fixed in 2026.2.22

Description

Summary Feishu allowlist authorization could be bypassed by display-name collision. Details `channels.feishu.allowFrom` is documented as an ID-based allowlist (open_id list), but Feishu policy matching accepted mutable sender display names in the same namespace. An attacker could set a display name equal to an allowlisted ID string and pass authorization checks. The fix enforces ID-only matching for Feishu allowlist checks, normalizes Feishu ID prefixes during comparison, and ignores mutable display names for authorization. Impact Deployments using Feishu allowlist-based authorization could incorrectly authorize non-allowlisted senders when a colliding display name was used. Affected Packages / Versions • Package: `openclaw` (npm) • Latest published version at triage time: `2026.2.21-2` • Affected range: `= 2026.2.22` Fix Commit(s) • `4ed87a667263ed2d422b9d5d5a5d326e099f92c7` Release Process Note `patched_versions` is pre-set to the planned next release (`>= 2026.2.22`) so the advisory is ready to publish once that npm release is available. OpenClaw thanks @jiseoung for reporting.

Related

Alias · CVE (1)

  • CVE-2026-32021 OpenClaw versions prior to 2026.2.22 contain an authorization bypass vulnerability in the Feishu allowFrom allowlist implementation that… vulnerability

Weakness · CWE (2)

  • CWE-639 Authorization Bypass Through User-Controlled Key weakness
  • CWE-863 Incorrect Authorization weakness

References