Loading vulnerability…
matrix-sdk-crypto before 0.16.1 fails to verify the sender's user ID when decrypting an Olm-encrypted to-device message that contains the sender_device_keys property. Because sender binding is incomplete in this code path, a malicious actor can cause the recipient to accept a forged sender identity for an encrypted to-device message. The issue affects the Matrix Rust SDK crypto crate distributed via crates.io and is tracked as GHSA-wfq4-36m3-9g42.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.