matrix-sdk-crypto contains a log exposure of private key of the server-side key backup

Exploitation

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

CVSS

5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-34353: 0.19% estimated exploitation activity in the next 30 days; percentile 9.10 (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.

Introduction In Matrix, the server-side key backup stores encrypted copies of Matrix message keys. This facilitates key sharing between a user's devices and provides a redundant copy in case all devices are lost. The key backup uses asymmetric cryptography, with each server-side key backup assigned a unique public-private key pair. Impact Due to a logic bug introduced in https://github.com/matrix-org/matrix-rust-sdk/pull/2961/commits/71136e44c03c79f80d6d1a2446673bc4d53a2067, the matrix-sdk-crypto crate version 0.7.0 will sometimes log the private part of the backup key pair to Rust debug logs (using the tracing crate). Patches This issue has been resolved in matrix-sdk-crypto version 0.7.1. Workarounds None. References - crates.io release For more information If you have any questions or comments about this advisory, please email us at security at matrix.org.

Published by the source

13 May 2024, 16:04 UTC

Last modified by the source

14 May 2024, 20:06 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9ggc-845v-gcgv

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

# Patch Next advisory brief: CVE-2024-34353

Advisory: matrix-sdk-crypto contains a log exposure of private key of the server-side key backup
IDs: CVE-2024-34353, GHSA-9ggc-845v-gcgv
Record: https://patchnext.com/advisories/cve-2024-34353 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: matrix-sdk-crypto 0.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io matrix-sdk-crypto: affected >= 0.7.0, <= 0.7.0; fixed in 0.7.1

## Suggested inspection (read-only)
- crates.io matrix-sdk-crypto: check the installed version with your package manager.

## 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-sdk-crypto.
- 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://github.com/advisories/GHSA-9ggc-845v-gcgv (GitHub-reviewed advisory GHSA-9ggc-845v-gcgv lists affected ranges: crates.io matrix-sdk-crypto >=0.7.0 <=0.7.0)

Commands are suggestions: review each one before running it.