Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-29628 | matrix-js-sdk has insufficient validation when considering a room to be upgraded by another |
Github GHSA |
GHSA-mp7c-m3rh-r56v | matrix-js-sdk has insufficient validation when considering a room to be upgraded by another |
Wed, 17 Sep 2025 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Matrix-org
Matrix-org matrix-js-sdk |
|
| Vendors & Products |
Matrix-org
Matrix-org matrix-js-sdk |
Tue, 16 Sep 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 16 Sep 2025 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Matrix JavaScript SDK is a Matrix Client-Server SDK for JavaScript and TypeScript. matrix-js-sdk before 38.2.0 has insufficient validation of room predecessor links in MatrixClient::getJoinedRooms, allowing a remote attacker to attempt to replace a tombstoned room with an unrelated attacker-supplied room. The issue has been patched and users should upgrade to 38.2.0. A workaround is to avoid using MatrixClient::getJoinedRooms in favor of getRooms() and filtering upgraded rooms separately. | |
| Title | matrix-js-sdk has insufficient validation when considering a room to be upgraded by another | |
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-09-16T18:26:33.217Z
Reserved: 2025-09-09T15:23:16.327Z
Link: CVE-2025-59160
Updated: 2025-09-16T17:29:40.082Z
Status : Deferred
Published: 2025-09-16T17:15:41.590
Modified: 2026-04-15T00:35:42.020
Link: CVE-2025-59160
No data.
OpenCVE Enrichment
Updated: 2025-09-17T10:52:10Z
EUVD
Github GHSA