{"answers":{"affected":"1 open source package ship an affected version, including matrix-sdk-crypto.","exploited":"There is no known exploitation of RUSTSEC-2026-0318 in the wild and no public exploit code.","fix":"Upgrade matrix-sdk-crypto to 0.19.0 or later.","what":"RUSTSEC-2026-0318 is a denial of service vulnerability in matrix-sdk-crypto, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0318 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0318 is a denial of service vulnerability in matrix-sdk-crypto, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2026-0318 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- matrix-sdk-crypto (crates.io): affected from 0.0.0-0; fixed in 0.19.0\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/RUSTSEC-2026-0318/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0318/index.md)","id":"RUSTSEC-2026-0318","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0318/index.md","name":"RUSTSEC-2026-0318","record":{"aliases":["GHSA-45pr-7vv7-f64m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Rust encryption library","requires_auth":"none","summary":"A panic occurs in the Rust encryption library when using IdentityBasedStrategy with recipients lacking cross-signing keys, causing denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Using the `IdentityBasedStrategy` setting when calling\n`Device::encrypt_event_raw` or `OlmMachine::encrypt_content_for_devices` may\ncause a panic if the recipient does not have cross-signing keys.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Sending custom to-device messages may panics","id":"RUSTSEC-2026-0318","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.19.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"matrix-sdk-crypto","purl":"pkg:cargo/matrix-sdk-crypto","source":"RUSTSEC-2026-0318"}],"products":null,"published":"2026-09-29","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A panic occurs in the Rust encryption library when using IdentityBasedStrategy with recipients lacking cross-signing keys, causing denial of service.","url":"https://insights.sbomify.com/RUSTSEC-2026-0318/"}