Skip to content

← Public intelligence

crates.io package

matrix-sdk-base

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 1.3crates.ioPublished

    matrix-sdk-base denial of service via custom m.room.join_rules event values

    CVE-2025-66622 · GHSA-jj6p-3m75-g2p3

    Affected
    • crates.io matrix-sdk-base < 0.16.0
    Fixed in
    0.16.0· Vendor fix available
    Issue
    The matrix-sdk-base crate is unable to handle responses that include custom m.room.joinrules 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.

    Recommended action: Upgrade to 0.16.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Low, CVSS 2.7crates.ioPublished

    matrix-sdk-base: Panic in the RoomMember::normalized_power_level() method

    CVE-2025-59047 · GHSA-qhj8-q5r6-8q6j

    Affected
    • crates.io matrix-sdk-base < 0.14.1
    Fixed in
    0.14.1· Vendor fix available
    Issue
    In matrix-sdk-base before 0.14.1, calling the RoomMember::normalizedpowerlevel() method can cause a panic if a room member has a power level of Int::Min. Patches The issue is fixed in matrix-sdk-base 0.14.1. Workarounds The affected method isn’t used internally, so avoiding calling RoomMember::normalizedpowerlevel() prevents the panic.

    Recommended action: Upgrade to 0.14.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →