matrix-sdk-base denial of service via custom m.room.join_rules event values
The matrix-sdk-base crate is unable to handle responses that include custom m.room.join_rules values due to a serialization bug. This can be exploited to cause a denial-of-service condition, if a user is invited to a room with non-standard join rules, the crate's sync process will stall, preventing further processing for all rooms. ### Patches The issue is fixed in matrix-sdk-base 0.16.0. ### Workarounds Users can leave affected rooms on another client to mitigate the issue. ### References The issue was fixed in https://github.com/matrix-org/matrix-rust-sdk/pull/5924.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-66622US | high7.5 | — | ||
matrix-sdk-base is the base component to build a Matrix client library. Versions 0.14.1 and prior are unable to handle responses that include custom m.room.join_rules values due to… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/matrix-org/matrix-rust-sdkPACKAGE
- https://github.com/matrix-org/matrix-rust-sdk/commit/4ea0418abefab2aa93f8851a4d39c723e703e6b0WEB
- https://github.com/matrix-org/matrix-rust-sdk/pull/5924WEB
- https://github.com/matrix-org/matrix-rust-sdk/security/advisories/GHSA-jj6p-3m75-g2p3WEB
- https://nvd.nist.gov/vuln/detail/CVE-2025-66622ADVISORY
- https://rustsec.org/advisories/RUSTSEC-2025-0135.htmlWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan