Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

Malicious homeservers can steal message keys when the matrix-react-sdk user invites another user to a room

CVE-2024-47824GHSA-qcvh-p9jq-wp8v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (matrix-react-sdk 3.102.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-47824: 0.66% estimated exploitation activity in the next 30 days; percentile 51.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact matrix-react-sdk before 3.102.0 allows a malicious homeserver to potentially steal message keys for a room when a user invites another user to that room, via injection of a malicious device controlled by the homeserver. This is possible because matrix-react-sdk before 3.102.0 shared historical message keys on invite. Patches matrix-react-sdk 3.102.0 disables sharing message keys on invite by removing calls to the vulnerable functionality. Workarounds None. References The vulnerability in matrix-react-sdk is caused by calling MatrixClient.sendSharedHistoryKeys in matrix-js-sdk, which is inherently vulnerable to this sort of attack. This matrix-js-sdk vulnerability is tracked as CVE-2024-47080 / GHSA-4jf8-g8wp-cx7c. Given that this functionality is not specific to sharing message keys on invite, is optional, has to be explicitly called by the caller and has been independently patched in matrix-react-sdk by removing the offending calls, we believe it is proper to treat the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-qcvh-p9jq-wp8v

  2. Revision 2 · amended ·

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

  3. Revision 1 · created ·

    Published from osv record GHSA-qcvh-p9jq-wp8v

Agent brief

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

# Patch Next advisory brief: CVE-2024-47824

Advisory: Malicious homeservers can steal message keys when the matrix-react-sdk user invites another user to a room
IDs: CVE-2024-47824, GHSA-qcvh-p9jq-wp8v
Record: https://patchnext.com/advisories/cve-2024-47824 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: matrix-react-sdk 3.102.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm matrix-react-sdk: affected >= 3.18.0, < 3.102.0; fixed in 3.102.0

## Suggested inspection (read-only)
- `npm ls matrix-react-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-react-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-qcvh-p9jq-wp8v (OSV record GHSA-qcvh-p9jq-wp8v lists affected ranges: npm matrix-react-sdk >=3.18.0 <3.102.0 (fixed))
- Verified: https://github.com/advisories/GHSA-qcvh-p9jq-wp8v (GitHub-reviewed advisory GHSA-qcvh-p9jq-wp8v lists affected ranges: npm matrix-react-sdk >=3.18.0 <3.102.0)

Commands are suggestions: review each one before running it.

Loading voting…