Summary
matrix-js-sdk has insufficient validation when considering a room to be upgraded by another
Workarounds
Avoid using MatrixClient::getJoinedRooms in favour of getRooms() and filtering upgraded rooms separately.
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.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue has been patched and users should upgrade to 38.2.0.
Frequently Asked Questions
- What is CVE-2025-59160? CVE-2025-59160 is a medium-severity improper input validation vulnerability in matrix-js-sdk (npm), affecting versions < 38.2.0. It is fixed in 38.2.0. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of matrix-js-sdk are affected by CVE-2025-59160? matrix-js-sdk (npm) versions < 38.2.0 is affected.
- Is there a fix for CVE-2025-59160? Yes. CVE-2025-59160 is fixed in 38.2.0. Upgrade to this version or later.
- Is CVE-2025-59160 exploitable, and should I be worried? Whether CVE-2025-59160 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
- What actually determines whether CVE-2025-59160 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.
- How do I fix CVE-2025-59160? Upgrade
matrix-js-sdkto 38.2.0 or later.