Most recent entries from all

fkie_cve-2026-45056

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.

GHSA-wfq4-36m3-9g42 — Matrix Rust SDK: Sender-binding gaps in to-device and room-key attribution

Affected: crates.io: matrix-sdk-crypto

### Impact

The `matrix-sdk-crypto` crate before 0.16.1 is missing a check for the sender's user ID when decrypting an Olm-encrypted to-device message containing the `sender_device_keys` property.

This could be exploited to spoof the sender of an encrypted to-device message, but only if the attacker colludes with (or is) the homeserver operator.

### Patches

This issue is fixed in `matrix-sdk-crypto` 0.16.1.

### Workarounds

There are no known workarounds for the issue.

### References

This issue was fixed in https://github.com/matrix-org/matrix-rust-sdk/pull/6553.

### For more information

If you have any questions or comments about this advisory, please email us at [security at matrix.org](mailto:security@matrix.org).

RUSTSEC-2026-0159 — Sender-binding gaps in to-device messages

Affected: crates.io: matrix-sdk-crypto

The matrix-sdk-crypto crate before 0.16.1 is missing a check for the sender's user ID when decrypting an Olm-encrypted to-device message containing the sender_device_keys property.

This could be exploited to spoof the sender of an encrypted to-device message, but only if the attacker colludes with (or is) the homeserver operator.