{"answers":{"affected":"3 open source packages ship an affected version, including matrix-sdk-crypto.","exploited":"There is no known exploitation of CVE-2026-45056 in the wild and no public exploit code.","fix":"Upgrade matrix-sdk-crypto to 0.16.1 or later.","what":"CVE-2026-45056 is a medium-severity authentication bypass vulnerability in matrix-org matrix-rust-sdk, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-45056 and fix it if it is affected.\n\nWhat it is: CVE-2026-45056 is a medium-severity authentication bypass vulnerability in matrix-org matrix-rust-sdk, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-45056 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- matrix-sdk-crypto (crates.io): affected from 0.12.0; fixed in 0.16.1\n- matrix-sdk-crypto (crates.io): affected from 0.12.0; fixed in 0.16.1\n- matrix-sdk-crypto (crates.io): affected from 0.12.0; fixed in 0.16.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45056/ (Markdown: https://insights.sbomify.com/CVE-2026-45056/index.md)","id":"CVE-2026-45056","markdown":"https://insights.sbomify.com/CVE-2026-45056/index.md","name":"CVE-2026-45056","record":{"aliases":["GHSA-wfq4-36m3-9g42","RUSTSEC-2026-0159"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Matrix Rust SDK","requires_auth":"high_privilege","summary":"Attackers colluding with homeservers can forge encrypted to-device events by bypassing sender identity checks in the Matrix Rust SDK.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"matrix-sdk-crypto is a no-network-IO implementation of a state machine that handles end-to-end encryption for Matrix clients. Starting in version 0.12.0 and prior to version 0.17.0, the matrix-sdk-crypto crate was missing a check for the user ID when decrypting an Olm-encrypted event containing the `sender_device_keys` property. This could be exploited to forge an encrypted to-device event, but only if the attacker colludes with the homeserver operator. This issue is fixed in matrix-sdk-crypto 0.17.0. There are no known workarounds for the issue.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Matrix Rust SDK: Sender-binding gaps in to-device and room-key attribution","id":"CVE-2026-45056","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"matrix-sdk-ui: Incomplete edit validation","id":"CVE-2026-45057"},"packages":[{"ecosystem":"crates.io","fixed":["0.16.1"],"introduced":["0.12.0"],"last_affected":[],"package":"matrix-sdk-crypto","purl":null,"source":"GHSA-wfq4-36m3-9g42"},{"ecosystem":"crates.io","fixed":["0.16.1"],"introduced":["0.12.0"],"last_affected":[],"package":"matrix-sdk-crypto","purl":"pkg:cargo/matrix-sdk-crypto","source":"GHSA-wfq4-36m3-9g42"},{"ecosystem":"crates.io","fixed":["0.16.1"],"introduced":["0.12.0"],"last_affected":[],"package":"matrix-sdk-crypto","purl":"pkg:cargo/matrix-sdk-crypto","source":"RUSTSEC-2026-0159"}],"prev":{"headline":"CubeCart: Pre-Authenticated Password Reset Link Poisoning via HTTP Host Header","id":"CVE-2026-45055"},"products":["matrix-rust-sdk"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["matrix-org"]},"summary":"Attackers colluding with homeservers can forge encrypted to-device events by bypassing sender identity checks in the Matrix Rust SDK.","url":"https://insights.sbomify.com/CVE-2026-45056/"}