CVE-2026-100541

OpenClaw Matrix before 2026.8.1 Authorization Bypass via Case Folding

Published Sep 26, 2026 CVSS 4.0 · 7.7 High EPSS < 1% KEV · Not listed

Description

OpenClaw's Matrix integration (npm package @openclaw/matrix) versions >= 2026.2.2 and < 2026.8.1 lowercase complete Matrix user IDs — including historical localparts and the case-sensitive server-name portion — when deriving the OpenClaw authorization identity. As a result, distinct authenticated Matrix accounts can normalize to the same authorization identity. A Matrix participant controlling a colliding account identifier (a protocol-valid identifier that differs from the configured one only by characters OpenClaw case/Unicode folds; display-name matching is not required) can inherit allowlist, owner-command, exec-approval, or plugin-approval authority configured for another account. The issue is fixed in 2026.8.1.

Analysis

Technical impact

OpenClaw's Matrix integration (npm package @openclaw/matrix) normalizes Matrix user IDs to lowercase when building the authorization identity, causing distinct accounts that differ only by case or Unicode folding to resolve to the same identity. This permits a Matrix user that owns a colliding identifier to inherit the allowlist, owner-command, exec‑approval, or plugin‑approval privileges that were configured for another account, effectively bypassing authorization controls. The flaw is a case‑folding oversight (CWE‑178).

Affected Systems

The vulnerability affects OpenClaw Matrix (npm package @openclaw/matrix) versions that are greater than or equal to 2026.2.2 and less than 2026.8.1. Any installation of the openclaw:matrix product within this version range is susceptible.

Risk and Exploitability

The vulnerability carries a CVSS score of 7.7, indicating moderate-to-high severity. Exploitability is not documented in EPSS or KEV, but the flaw can be leveraged by any user who can create or control a Matrix account that collides with a pre‑existing one, allowing that user to obtain elevated authorities on the target system. Attack requires authentication to Matrix and the ability to register or manage a colliding account, making the threat actionable to insiders or compromised accounts.

Affected Products

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

openclaw

matrix

unaffected

Version	Status	Constraints
`2026.2.2`	affected	< 2026.8.1
`2026.8.1`	unaffected	—

No data.

Vendor Product Versions

Openclaw

Matrix

Version	Status	Scheme	Platform
`[2026.2.2,2026.8.1)`	affected	semver	—
`2026.8.1`	unaffected	semver	—

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

Upgrade @openclaw/matrix to version 2026.8.1 or later.
Validate that all existing Matrix account identifiers are unique and do not collide after the upgrade.
Revoke and re‑issue credentials for accounts that could have collided to ensure distinct authorization identities.

Generated by OpenCVE AI on September 26, 2026 at 03:35 UTC.

Tracking

Advisories

No advisories available

Metrics

Attack Vector Network

Attack Complexity High

Privileges Required Low

Attack Requirements Present

User Interaction None

Vulnerable System Confidentiality Impact High

Vulnerable System Integrity Impact High

Vulnerable System Availability Impact High

Subsequent System Confidentiality Impact None

Subsequent System Integrity Impact None

Subsequent System Availability Impact None

Attack Vector Network

Attack Complexity High

Privileges Required Low

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploit prediction score: < 1% (0.303% probability within 30 days)

Exploitation none

Automatable no

Technical Impact total

References

Link	Providers
https://github.com/openclaw/openclaw/security/advisories/GHSA-hgv5-f2r3-6v9r
https://www.vulncheck.com/advisories/openclaw-matrix-before-2026.8.1-authorization-bypass-via-case-folding

History

Sep 29, 2026 6:30 PM Scoring metrics updated View changes

Type	Values Removed	Values Added
Metrics		ssvc `{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}`

Sep 26, 2026 11:00 PM First appearance in the feed. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Openclaw Openclaw matrix
Vendors & Products		Openclaw Openclaw matrix

Sep 26, 2026 2:30 AM Description updated. Title updated. Weaknesses updated. Added references. Scoring metrics updated View changes

Type	Values Removed	Values Added
Description		OpenClaw's Matrix integration (npm package @openclaw/matrix) versions >= 2026.2.2 and < 2026.8.1 lowercase complete Matrix user IDs — including historical localparts and the case-sensitive server-name portion — when deriving the OpenClaw authorization identity. As a result, distinct authenticated Matrix accounts can normalize to the same authorization identity. A Matrix participant controlling a colliding account identifier (a protocol-valid identifier that differs from the configured one only by characters OpenClaw case/Unicode folds; display-name matching is not required) can inherit allowlist, owner-command, exec-approval, or plugin-approval authority configured for another account. The issue is fixed in 2026.8.1.
Title		OpenClaw Matrix before 2026.8.1 Authorization Bypass via Case Folding
Weaknesses		CWE-178
References		https://github.com/openclaw/openclaw/security/advisories/GHSA-hgv5-f2r3-6v9r https://www.vulncheck.com/advisories/openclaw-matrix-before-2026.8.1-authorization-bypass-via-case-folding
Metrics		cvssV3_1 `{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}` cvssV4_0 `{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}`