CVE-2026-28471

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.example and @alice:trusted.example both match alice

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.

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.

Matrix DM allowlist identity confusion. The practical impact depends on your Matrix channel policies and what capabilities are enabled downstream.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-28471 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-28471? CVE-2026-28471 is a medium-severity improper authentication vulnerability in openclaw (npm), affecting versions >= 2026.1.14-1, < 2026.2.2. It is fixed in 2026.2.2. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-28471? CVE-2026-28471 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-28471? openclaw (npm) versions >= 2026.1.14-1, < 2026.2.2 is affected.
4. Is there a fix for CVE-2026-28471? Yes. CVE-2026-28471 is fixed in 2026.2.2. Upgrade to this version or later.
5. Is CVE-2026-28471 exploitable, and should I be worried? Whether CVE-2026-28471 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-28471 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-28471? Upgrade openclaw to 2026.2.2 or later.