CVE-2026-45057 affects the Rust crate matrix-sdk-ui before version 0.16.1. The flaw is in the message edit validation logic for Matrix replacement events: when an encrypted event is replaced, the SDK did not enforce that the replacement event was also encrypted. This incomplete validation allows a crafted unencrypted replacement event to be accepted in place of an encrypted original event, contrary to the expected validation rules for encrypted message edits. As a result, a malicious homeserver administrator, or another actor with equivalent control over event delivery or modification, can cause clients using vulnerable versions of matrix-sdk-ui to display spoofed edited messages as though they were authored by the victim user.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
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.