matrix-js-sdk has insufficient validation when considering a room to be upgraded by another

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-59160: 0.24% estimated exploitation activity in the next 30 days; percentile 15.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

16 Sep 2025, 20:18 UTC

Last modified by the source

22 Sep 2025, 22:59 UTC

Source last checked

26 Oct 2026, 12:38 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-mp7c-m3rh-r56v

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-mp7c-m3rh-r56v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-59160

Advisory: matrix-js-sdk has insufficient validation when considering a room to be upgraded by another
IDs: CVE-2025-59160, GHSA-mp7c-m3rh-r56v
Record: https://patchnext.com/advisories/cve-2025-59160 (revision 3, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: matrix-js-sdk 38.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm matrix-js-sdk: affected < 38.2.0; fixed in 38.2.0

## Suggested inspection (read-only)
- `npm ls matrix-js-sdk --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on matrix-js-sdk.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mp7c-m3rh-r56v (OSV record GHSA-mp7c-m3rh-r56v lists affected ranges: npm matrix-js-sdk >=0 <38.2.0 (fixed))
- Verified: https://github.com/advisories/GHSA-mp7c-m3rh-r56v (GitHub-reviewed advisory GHSA-mp7c-m3rh-r56v lists affected ranges: npm matrix-js-sdk >=0 <38.2.0)

Commands are suggestions: review each one before running it.