How severe is GHSA-mp7c-m3rh-r56v?

No CVSS score has been assigned to GHSA-mp7c-m3rh-r56v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mp7c-m3rh-r56v?

GHSA-mp7c-m3rh-r56v affects the following packages: matrix-js-sdk (npm). Ecosystems affected: npm.

How do I fix GHSA-mp7c-m3rh-r56v?

Update matrix-js-sdk to 38.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mp7c-m3rh-r56v is resolved across your whole dependency graph.

How do I detect GHSA-mp7c-m3rh-r56v in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-js-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mp7c-m3rh-r56v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mp7c-m3rh-r56v?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mp7c-m3rh-r56v can be triaged on real exposure rather than presence alone.

Is GHSA-mp7c-m3rh-r56v actively exploited in the wild?

No public exploit code has been indexed for GHSA-mp7c-m3rh-r56v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mp7c-m3rh-r56v?

GHSA-mp7c-m3rh-r56v has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-mp7c-m3rh-r56v?

GHSA-mp7c-m3rh-r56v is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mp7c-m3rh-r56v published, and has it been updated?

GHSA-mp7c-m3rh-r56v was published on September 16, 2025 and was last updated on September 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-mp7c-m3rh-r56v — matrix-js-sdk

Fix: matrix-org/matrix-js-sdk@43c72d5

GHSA-mp7c-m3rh-r56v is a CWE-345 vulnerability in matrix-js-sdk. A fix is available for matrix-js-sdk — see the affected versions and patch details below.

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

Also known asCVE-2025-59160

Published

Sep 16, 2025

Updated

Sep 22, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mp7c-m3rh-r56v.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

163other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

matrix-js-sdknpm

1.1Mdownloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`matrix-js-sdk`	all versions	38.2.0`npm install matrix-js-sdk@38.2.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-js-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update matrix-js-sdk to 38.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mp7c-m3rh-r56v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mp7c-m3rh-r56v can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mp7c-m3rh-r56v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-mp7c-m3rh-r56v in your dependencies?

O3 Security finds GHSA-mp7c-m3rh-r56v across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works