https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 14:38:49 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32021 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions prior to 2026.2.22 contain an authorization bypass vulnerability in the Feishu allowFrom allowlist implementation that accepts mutable sender display names instead of enforcing ID-only matching. An attacker can set a display name equal to an allowlisted ID string to bypass authorization checks and gain unauthorized access.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions prior to 2026.2.22 contain an authorization bypass vulnerability in the Feishu allowFrom allowlist implementation that accepts mutable sender display names instead of enforcing ID-only matching. An attacker can set a display name equal to an allowlisted ID string to bypass authorization checks and gain unauthorized access.</p> https://vulnerability.circl.lu/vuln/cve-2026-32021 https://vulnerability.circl.lu/vuln/ghsa-j4xf-96qf-rx69 <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>Feishu allowlist authorization could be bypassed by display-name collision.</p> <p>### Details</p> <p>`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.</p> <p>The fix enforces ID-only matching for Feishu allowlist checks, normalizes Feishu ID prefixes during comparison, and ignores mutable display names for authorization.</p> <p>### Impact</p> <p>Deployments using Feishu allowlist-based authorization could incorrectly authorize non-allowlisted senders when a colliding display name was used.</p> <p>### Affected Packages / Versions</p> <p>- Package: `openclaw` (npm) - Latest published version at triage time: `2026.2.21-2` - Affected range: `&lt;= 2026.2.21-2` - Planned patched version: `&gt;= 2026.2.22`</p> <p>### Fix Commit(s)</p> <p>- `4ed87a667263ed2d422b9d5d5a5d326e099f92c7`</p> <p>### Release Process Note</p> <p>`patched_versions` is pre-set to the planned next release (`&gt;= 2026.2.22`) so the advisory is ready to publish once that npm release is available.</p> <p>OpenClaw thanks @jiseoung for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>### Summary</p> <p>Feishu allowlist authorization could be bypassed by display-name collision.</p> <p>### Details</p> <p>`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.</p> <p>The fix enforces ID-only matching for Feishu allowlist checks, normalizes Feishu ID prefixes during comparison, and ignores mutable display names for authorization.</p> <p>### Impact</p> <p>Deployments using Feishu allowlist-based authorization could incorrectly authorize non-allowlisted senders when a colliding display name was used.</p> <p>### Affected Packages / Versions</p> <p>- Package: `openclaw` (npm) - Latest published version at triage time: `2026.2.21-2` - Affected range: `&lt;= 2026.2.21-2` - Planned patched version: `&gt;= 2026.2.22`</p> <p>### Fix Commit(s)</p> <p>- `4ed87a667263ed2d422b9d5d5a5d326e099f92c7`</p> <p>### Release Process Note</p> <p>`patched_versions` is pre-set to the planned next release (`&gt;= 2026.2.22`) so the advisory is ready to publish once that npm release is available.</p> <p>OpenClaw thanks @jiseoung for reporting.</p> https://vulnerability.circl.lu/vuln/ghsa-j4xf-96qf-rx69