← Back
CVE-2026-45056
Vulnerability in matrix-sdk-crypto (CVE-2026-45056)
Summary
vulnerability in matrix-sdk-crypto (CVE-2026-45056). Risk of unauthorized operations or information disclosure. Exploitable via ``sender_device_keys``. Mitigation: upgrade to `0.16.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45056** has been found in matrix-sdk-crypto.
Attackers can target a specific entry point like ``sender_device_keys`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade matrix-sdk-crypto to **0.16.1** or later.
If unsure, ask your IT team or search "matrix-sdk-crypto CVE-2026-45056" on the vendor's site.
CVE-2026-45056 (matrix-sdk-crypto) — CWE-290 /
Attack surface: `sender_device_keys`
Patched: `0.16.1` — apply immediately
Workaround: There are no known workarounds for the issue.
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.
❓ What is the problem
**A vulnerability** (CWE-290) exists in matrix-sdk-crypto. Attackers reach the vulnerable code path via ``sender_device_keys`` without authentication.
📍 Affected scope
matrix-sdk-crypto — . Attack surface: `sender_device_keys`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.16.1**.
🛡️ Workaround
Workaround: There are no known workarounds for the issue.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'matrix-sdk-crypto' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'matrix-sdk-crypto' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `matrix-sdk-crypto` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There are no known workarounds for the issue.パッチが適用されるまでの応急処置として、There are no known workarounds for the issue. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade matrix-sdk-crypto to 0.16.1ステージング環境で 0.16.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
matrix-sdk-crypto
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.16.1"}]}]
crates.io
matrix-sdk-crypto
[{"type":"SEMVER","events":[{"introduced":"0.12.0"},{"fixed":"0.16.1"}]}]
References
- package https://crates.io/crates/matrix-sdk-crypto
- package https://github.com/matrix-org/matrix-rust-sdk
- web https://github.com/matrix-org/matrix-rust-sdk/security/advisories/GHSA-wfq4-36m3-9g42
- web https://github.com/matrix-org/matrix-rust-sdk/pull/6553
- web https://github.com/matrix-org/matrix-rust-sdk/releases/tag/matrix-sdk-0.16.1
- web https://rustsec.org/advisories/RUSTSEC-2026-0159.html
- web https://github.com/advisories/GHSA-wfq4-36m3-9g42