matrix-js-sdk has insufficient validation when considering a room to be upgraded by another
### Impact 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. ### Patches The issue has been patched and users should upgrade to 38.2.0. ### Workarounds Avoid using `MatrixClient::getJoinedRooms` in favour of `getRooms()` and filtering upgraded rooms separately.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-59160US | —OT elevated | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/matrix-org/matrix-js-sdkPACKAGE
- https://github.com/matrix-org/matrix-js-sdk/commit/43c72d5bf5e2d0a26b3b4f71092e7cb39d4137c4WEB
- https://github.com/matrix-org/matrix-js-sdk/releases/tag/v38.2.0WEB
- https://github.com/matrix-org/matrix-js-sdk/security/advisories/GHSA-mp7c-m3rh-r56vWEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-59160ADVISORY
- https://www.npmjs.com/package/matrix-js-sdk/v/38.2.0WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan