How severe is GHSA-4jf8-g8wp-cx7c?

No CVSS score has been assigned to GHSA-4jf8-g8wp-cx7c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4jf8-g8wp-cx7c?

GHSA-4jf8-g8wp-cx7c affects the following packages: matrix-js-sdk (npm). Ecosystems affected: npm.

How do I fix GHSA-4jf8-g8wp-cx7c?

Update matrix-js-sdk to 34.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jf8-g8wp-cx7c is resolved across your whole dependency graph.

How do I detect GHSA-4jf8-g8wp-cx7c 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-4jf8-g8wp-cx7c if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-4jf8-g8wp-cx7c actively exploited in the wild?

No public exploit code has been indexed for GHSA-4jf8-g8wp-cx7c 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-4jf8-g8wp-cx7c?

GHSA-4jf8-g8wp-cx7c has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th 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-4jf8-g8wp-cx7c?

GHSA-4jf8-g8wp-cx7c is classified as Information Exposure (CWE-200), Improper Authentication (CWE-287). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4jf8-g8wp-cx7c published, and has it been updated?

GHSA-4jf8-g8wp-cx7c was published on October 15, 2024 and was last updated on October 15, 2024. 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

Matrix JavaScript SDK's key history sharing could share keys to malicious devicesGHSA-4jf8-g8wp-cx7c

Fix: matrix-org/matrix-spec-proposals#3061

GHSA-4jf8-g8wp-cx7c is a Information Exposure vulnerability in matrix-js-sdk. A fix is available for matrix-js-sdk — see the affected versions and patch details below.

Also known asCVE-2024-47080

Published

Oct 15, 2024

Updated

Oct 15, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-4jf8-g8wp-cx7c.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

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

matrix-js-sdknpm

488Kdownloads / week

Description

Impact

In matrix-js-sdk versions 9.11.0 through 34.7.0, the method MatrixClient.sendSharedHistoryKeys is vulnerable to interception by malicious homeservers. The method implements functionality proposed in MSC3061 and can be used by clients to share historical message keys with newly invited users, granting them access to past messages in the room.

However, it unconditionally sends these "shared" keys to all of the invited user's devices, regardless of whether the user's cryptographic identity is verified or whether the user's devices are signed by that identity. This allows the attacker to potentially inject its own devices to receive sensitive historical keys without proper security checks.

Note that this only affects clients running the SDK with the legacy crypto stack. Clients using the new Rust cryptography stack (i.e. those that call MatrixClient.initRustCrypto() instead of MatrixClient.initCrypto()) are unaffected by this vulnerability, because MatrixClient.sendSharedHistoryKeys() raises an exception in such environments.

Patches

Fixed in matrix-js-sdk 34.8.0 by removing the vulnerable functionality.

Workarounds

Remove use of affected functionality from clients.

References

MSC3061

For more information

If you have any questions or comments about this advisory, please email us at security at matrix.org.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`matrix-js-sdk`	≥ 9.11.0&&< 34.8.0	34.8.0`npm install matrix-js-sdk@34.8.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 34.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jf8-g8wp-cx7c is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact In matrix-js-sdk versions 9.11.0 through 34.7.0, the method `MatrixClient.sendSharedHistoryKeys` is vulnerable to interception by malicious homeservers. The method implements functionality proposed in [MSC3061](https://github.com/matrix-org/matrix-spec-proposals/pull/3061) and can be used by clients to share historical message keys with newly invited users, granting them access to past messages in the room. However, it unconditionally sends these "shared" keys to all of the invited user's devices, regardless of whether the user's cryptographic identity is verified or whether the u

O3 Security · Impact-Aware SCA

Is GHSA-4jf8-g8wp-cx7c in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works