CVE-2026-28471: OpenClaw has a Matrix allowlist bypass via displayName and cross-homeserver localpart matching
Summary OpenClaw Matrix DM allowlist matching could be bypassed in certain configurations. Matrix support ships as an optional plugin (not bundled with the core install), so this only affects deployments that have installed and enabled the Matrix plugin.
Published Feb 17, 2026 · Updated Mar 6, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- >= 2026.1.14-1, < 2026.2.2
- Fixed in
- 2026.2.2
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
OpenClaw Matrix DM allowlist matching could be bypassed in certain configurations.
Matrix support ships as an optional plugin (not bundled with the core install), so this only affects deployments that have installed and enabled the Matrix plugin.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
>= 2026.1.14-1, < 2026.2.2 - Patched:
>= 2026.2.2
Details
In affected versions, DM allowlist decisions could be made by exact-matching channels.matrix.dm.allowFrom entries against multiple sender-derived candidates, including:
- The sender display name (attacker-controlled and non-unique)
- The sender MXID localpart with the homeserver discarded, so
@alice:evil.exampleand@alice:trusted.exampleboth matchalice
If an operator configured channels.matrix.dm.allowFrom with display names or bare localparts (for example, "Alice" or "alice"), a remote Matrix user may be able to impersonate an allowed identity for allowlist purposes and reach the routing/agent pipeline.
Impact
Matrix DM allowlist identity confusion. The practical impact depends on your Matrix channel policies and what capabilities are enabled downstream.
Mitigation
- Upgrade to
openclaw >= 2026.2.2. - Ensure Matrix allowlists contain only full Matrix user IDs (MXIDs) like
@user:server(or*). Do not use display names or bare localparts.
Fix Commit(s)
8f3bfbd1c4fb967a2ddb5b4b9a05784920814bcf
Release Process Note
The patched version is already published to npm; the advisory can be published once you're ready.
Thanks @MegaManSec (https://joshua.hu) of AISLE Research Team for reporting.
Credited to MegaManSec.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-rmxw-jxxx-4cpc
- https://github.com/openclaw/openclaw/commit/8f3bfbd1c4fb967a2ddb5b4b9a05784920814bcf
- https://github.com/openclaw/openclaw/releases/tag/v2026.2.2
- https://nvd.nist.gov/vuln/detail/CVE-2026-28471
- https://www.vulncheck.com/advisories/openclaw-allowlist-bypass-via-displayname-and-cross-homeserver-localpart-matching-in-matrix
- https://github.com/advisories/GHSA-rmxw-jxxx-4cpc
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
