Skip to content

GHSA-wfq4-36m3-9g42 CVE-2026-45056 RUSTSEC-2026-0159

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

Medium crates.io
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.31%
Chance of exploitation in the next 30 days. Higher than 23.61% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-290 Authentication Bypass by Spoofing
Fix
0.16.1
Upgrade matrix-sdk-crypto to this version or later

Description

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.

Affected versions

crates.io

PackageVulnerableFixed in
matrix-sdk-crypto
>= 0.12.0, < 0.16.1
0.16.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

matrix-sdk-crypto crates.io → 0.16.1

cargo
cargo update -p matrix-sdk-crypto --precise 0.16.1

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
High
User interaction
None
Confidentiality (vulnerable system)
None
Integrity (vulnerable system)
High
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

Weakness

CWE-290: Authentication Bypass by Spoofing

This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
RUSTSEC-2026-0318
Sending custom to-device messages may panics
Not rated yet Also affects matrix-sdk-crypto
GHSA-x958-rvg6-956w
matrix-sdk-crypto vulnerable to sender of encrypted events being spoofed by homeserver administrator
Medium Also affects matrix-sdk-crypto
GHSA-4qg4-cvh2-crgg
matrix-sdk-crypto's `UserIdentity::is_verified` not checking verification status of own user identity while performing the check
Medium Also affects matrix-sdk-crypto
GHSA-9ggc-845v-gcgv
matrix-sdk-crypto contains a log exposure of private key of the server-side key backup
Medium Also affects matrix-sdk-crypto
GHSA-r5vf-wf4h-82gg
matrix-sdk-crypto missing facility to signal rotation of a verified cryptographic identity
Medium Also affects matrix-sdk-crypto
GHSA-vp68-2wrm-69qm
matrix-sdk-crypto contains potential impersonation via room key forward responses
High Also affects matrix-sdk-crypto
CVE-2026-102764
The vulnerability exists within internal components of BeyondTrust’s Remote Support product.
Critical Known exploited Same weakness, CWE-290
CVE-2026-104935
Authentication bypass by spoofing in ICS before version 25.1.3.0 allows a remote unauthenticated attacker to execute arbitrary commands.
High Known exploited Same weakness, CWE-290
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor