Advisory

GHSA-wfq4-36m3-9g42

Also known as: CVE-2026-45056, RUSTSEC-2026-0159

Summary

Matrix Rust SDK: Sender-binding gaps in to-device and room-key attribution

Details

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:[email protected]).

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-04 14:47 UTC
Modified
2026-06-04 15:00 UTC

Affected packages and fixes

matrix-sdk-crypto

crates.io · All systems

Affected

  • introduced 0.12.0, fixed 0.16.1 (semver)

Fixed versions

0.16.1

Fix

  • Fixed version 0.16.1
    cargo update -p matrix-sdk-crypto --precise 0.16.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences