Rust advisories / crate
Security history · matrix-sdk-crypto · data from Oct 24, 2026
Is matrix-sdk-crypto safe to use? Its security history
VerdictNo open advisories. 6 past vulnerabilities were fixed; use 0.19.0 or newer to be clear of all of them.
7advisories on record
6vulnerabilities
0unmaintained notices
0.19.0newest fixed version
Every advisory, newest first
- VulnerabilityRUSTSEC-2026-0318 · 2026-09-29Sending custom to-device messages may panics
- VulnerabilityRUSTSEC-2026-0159 · 2026-06-03Sender-binding gaps in to-device messages
- Vulnerability MediumRUSTSEC-2025-0041 · 2025-06-11matrix-sdk-crypto vulnerable to encrypted event sender spoofing by homeserver administrator
- VulnerabilityRUSTSEC-2024-0356 · 2024-07-18`UserIdentity::is_verified` not checking verification status of own user identity while performing the check
- VulnerabilityGHSA-9ggc-845v-gcgv · 2024-05-13matrix-sdk-crypto contains a log exposure of private key of the server-side key backup
- NoticeRUSTSEC-2024-0434 · 2024-01-07 Missing facility to signal rotation of a verified cryptographic identity
- Vulnerability HighRUSTSEC-2022-0085 · 2022-09-29matrix-sdk Impersonation of room keys
Check your version
Run cargo tree -i matrix-sdk-crypto to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?