Vulnerability in matrix-sdk-base (CVE-2025-66622)
Summary
Vulnerability in matrix-sdk-base (CVE-2025-66622). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-66622 has been found in matrix-sdk-base.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "matrix-sdk-base CVE-2025-66622" on the vendor's site.
CVE-2025-66622 (matrix-sdk-base) — CWE-755 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-755) exists in matrix-sdk-base.
Check the vendor advisory for the affected versions of matrix-sdk-base.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'matrix-sdk-base' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'matrix-sdk-base' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
matrix-sdk-baseを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory rustsec.org
- package crates.io
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com