Advisory record · GHSA-wfq4-36m3-9g42

Sender-binding gaps in to-device messages

CVSS 6.9 MediumEPSS 0.0031 · 23rd percentile

Published by the GitHub Advisory Database at 3 Jun 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
matrix-sdk-cryptocrates.io>=0.12.0, <0.16.10.16.1
Identifiers
GHSA-wfq4-36m3-9g42 · CVE-2026-45056 · RUSTSEC-2026-0159
Weakness (CWE)
CWE-290
Published
3 Jun 2026
Updated
12 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The matrix-sdk-crypto crate, versions 0.12.0 up to but not including 0.16.1, does not check the sender's user ID when decrypting Olm-encrypted to-device messages that contain the sender_device_keys property. An attacker who colludes with or is the homeserver operator could spoof the sender of an encrypted to-device message. Upgrade to matrix-sdk-crypto 0.16.1.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 23rd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.