Matrix Rust Sdk
Approved changes feed: RSS · Atom
cpe:2.3:a:matrix-org:matrix-rust-sdk:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Matrix Org (d88e1973-fb17-5e22-857e-e34f791696f0) |
|---|---|
| Product | Matrix Rust Sdk (a59b6321-ac73-5574-846f-14631b5d0218) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-45056 |
vulnerable | 2026-09-16 04:33:58.174748 |
Matrix Rust SDK: Sender-binding gaps in to-device and room-key attribution
matrix-sdk-crypto is a no-network-IO implementation of a state machine that handles end-to-end encryption for Matrix clients. Starting in version 0.12.0 and prior to version 0.17.0, the matrix-sdk-crypto crate was missing a check for the user ID when decrypting an Olm-encrypted event containing the `sender_device_keys` property. This could be exploited to forge an encrypted to-device event, but only if the attacker colludes with the homeserver operator. This issue is fixed in matrix-sdk-crypto 0.17.0. There are no known workarounds for the issue.
Published: 2026-09-11T21:13:56.332Z
Updated: 2026-09-14T18:17:31.910Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-66622 |
vulnerable | 2026-06-08 07:41:19.352029 |
matrix-sdk-base is vulnerable to DoS via custom m.room.join_rules event values
matrix-sdk-base is the base component to build a Matrix client library. Versions 0.14.1 and prior are unable to handle responses that include custom m.room.join_rules values due to a serialization bug. This can be exploited to cause a denial-of-service condition, if a user is invited to a room with non-standard join rules, the crate's sync process will stall, preventing further processing for all rooms. This is fixed in version 0.16.0.
Published: 2025-12-09T02:07:18.831Z
Updated: 2025-12-09T16:02:47.455Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59047 |
vulnerable | 2026-06-08 07:35:19.946665 |
matrix-sdk-base has panic in the `RoomMember::normalized_power_level()` method
matrix-sdk-base is the base component to build a Matrix client library. In matrix-sdk-base before 0.14.1, calling the `RoomMember::normalized_power_level()` method can cause a panic if a room member has a power level of `Int::Min`. The issue is fixed in matrix-sdk-base 0.14.1. The affected method isn’t used internally, so avoiding calling `RoomMember::normalized_power_level()` prevents the panic.
Published: 2025-09-11T18:03:50.361Z
Updated: 2025-09-11T18:22:28.636Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-53549 |
vulnerable | 2026-06-08 07:31:14.704241 |
Matrix Rust SDK allows SQL injection in the EventCache implementation
The Matrix Rust SDK is a collection of libraries that make it easier to build Matrix clients in Rust. An SQL injection vulnerability in the EventCache::find_event_with_relations method of matrix-sdk 0.11 and 0.12 allows malicious room members to execute arbitrary SQL commands in Matrix clients that directly pass relation types provided by those room members into this method, when used with the default sqlite-based store backend. Exploitation is unlikely, as no known clients currently use the API in this manner. This vulnerability is fixed in 0.13.
Published: 2025-07-10T18:28:24.373Z
Updated: 2025-07-10T19:02:23.365Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-48937 |
vulnerable | 2026-06-08 07:29:12.271961 |
matrix-sdk-crypto vulnerable to sender of encrypted events being spoofed by homeserver administrator
MEDIUM (4.9)
matrix-rust-sdk is an implementation of a Matrix client-server library in Rust. matrix-sdk-crypto since version 0.8.0 and up to 0.11.0 does not correctly validate the sender of an encrypted event. Accordingly, a malicious homeserver operator can modify events served to clients, making those events appear to the recipient as if they were sent by another user. This vulnerability is fixed in 0.11.1 and 0.12.0.
Published: 2025-06-10T15:32:00.822Z
Updated: 2025-06-10T15:46:22.358Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-52813 |
vulnerable | 2026-06-08 06:52:16.272813 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-40648 |
vulnerable | 2026-06-08 06:43:52.832202 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-39252 |
vulnerable | 2026-06-08 05:47:18.436097 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.