CVE-2026-44110

Matrix room control-command authorization used the effective allowlist for room traffic, which included sender IDs learned from the Matrix DM pairing store. A sender who was allowed only for a Matrix DM could therefore authorize room control commands when they also posted in a bot room.

Affected versions

• Affected: > 2026.3.28, < 2026.4.15
• Patched: 2026.4.15

This bypass let a DM-paired Matrix sender cross the DM/room authorization boundary and run Matrix room control commands without being present in the configured room allowlist, room membership list, or group allowlist. The issue required a sender already present in the pairing store and able to send to the target Matrix room. Severity remains high because room control commands can drive privileged OpenClaw behavior depending on the deployment's command and tool policy.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-44110 has a CVSS score of 8.8 (High). The vector is network-reachable, low 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.4.15); upgrading removes the vulnerable code path.

Kodem intelligence

OpenClaw 2026.4.15 fixes the authorization boundary. Room control-command authorizers now use only configured sender IDs, effective room users, and group allowlists; DM pairing-store entries no longer authorize room commands. A follow-up change also skips DM pairing-store reads on room traffic.

Verified in v2026.4.15:

• extensions/matrix/src/matrix/monitor/access-state.ts builds room command authorizers from commandAllowFrom, which excludes pairing-store sender IDs for room traffic.
• extensions/matrix/src/matrix/monitor/handler.ts gates room control commands through those authorizers.
• extensions/matrix/src/matrix/monitor/access-state.test.ts covers a DM pairing-store sender and verifies it cannot authorize room control commands.

Fix commits included in v2026.4.15 and absent from v2026.4.14:

• f8705f512b09043df02b5da372c33374734bd921 via PR #67294
• 2bfd808a83116bd888e3e2633a61473fa2ed81b6 via PR #67325

Thanks to @nexrin and Keen Security Lab for reporting this issue.

1. What is CVE-2026-44110? CVE-2026-44110 is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions > 2026.3.28, < 2026.4.15. It is fixed in 2026.4.15. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-44110? CVE-2026-44110 has a CVSS score of 8.8 (High). 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-44110? openclaw (npm) versions > 2026.3.28, < 2026.4.15 is affected.
4. Is there a fix for CVE-2026-44110? Yes. CVE-2026-44110 is fixed in 2026.4.15. Upgrade to this version or later.
5. Is CVE-2026-44110 exploitable, and should I be worried? Whether CVE-2026-44110 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-44110 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-44110? Upgrade openclaw to 2026.4.15 or later.