Skip to main content

Matrix CVE-2025-66622

LOW
Improper Handling of Exceptional Conditions (CWE-755)
2025-12-09 security-advisories@github.com GHSA-jj6p-3m75-g2p3
1.3
CVSS 4.0 · Vendor: github
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Exception handling procedures
Impact

While the CVSS score of 7.5 indicates high severity due to network-based attacks requiring no authentication (AV:N/AC:L/PR:N/UI:N), the real-world risk appears moderate based on multiple factors. The EPSS score of 0.06% (19th percentile) suggests very low exploitation probability in the wild, and the vulnerability is not listed in CISA's KEV catalog indicating no known active exploitation. The attack vector requires an attacker to successfully invite a target user to a specially crafted room, which adds a social engineering component not reflected in the CVSS score. From an SSVC perspective, this appears to be a client-side DoS with no automation potential and limited technical impact beyond availability, making it a lower priority than the CVSS score suggests.

Exploit ScenarioDerived

An attacker creates a malicious Matrix room configured with custom or non-standard m.room.join_rules values, then invites target users to this room. When the victim's Matrix client attempts to process the invitation during its sync operation, the serialization bug causes the sync process to stall completely, preventing the user from receiving any further room updates or messages across all their rooms until the client is restarted. No proof-of-concept has been publicly disclosed, but the attack requires only the ability to create rooms and send invitations on the Matrix network.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 17, 2026

A serialization bug in matrix-sdk-base allows remote attackers to cause denial-of-service by sending rooms with custom m.room.join_rules values, which stalls the sync process and prevents all room processing. The vulnerability affects matrix-sdk-base versions 0.14.1 and prior and has a high availability impact (CVSS 7.5) with a patch available in version 0.16.0. With a low EPSS score of 0.06% and no KEV listing, this represents a moderate real-world risk primarily concerning service availability rather than active exploitation.

RemediationAI

Upgrade matrix-sdk-base to version 0.16.0 or later, which includes the fix implemented in commit 4ea0418abefab2aa93f8851a4d39c723e703e6b0 and pull request #5924. The patch is available from the vendor at https://github.com/matrix-org/matrix-rust-sdk/security/advisories/GHSA-jj6p-3m75-g2p3. As a temporary workaround until patching is possible, consider implementing application-level filtering to reject or quarantine room invitations containing non-standard join rules before they reach the SDK's sync process, though upgrading remains the recommended solution.

Affected Packages

cargo matrix-sdk-base fix: 0.16.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in cargo

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The matrix-sdk-base is a Rust library component used to build Matrix protocol clients, identified by CPE cpe:2.3:a:matrix:matrix-rust-sdk:*:*:*:*:*:*:*:*. The vulnerability stems from CWE-755 (Improper Handling of Exceptional Conditions), where the deserialization logic cannot properly handle non-standard or custom m.room.join_rules values in Matrix room state events. When the sync process encounters these malformed join rules during room invitation processing, it fails to deserialize the response correctly, causing the entire synchronization mechanism to halt and preventing the client from processing any further room updates across all rooms.

Know when Matrix gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 1.3 LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U

Primary rating from Vendor (github) · only source for this CVE.

CVSS VectorVendor: github

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

4
Severity Changed
Oct 07, 2026 - 20:22 NVD
HIGH LOW
CVSS changed
Oct 07, 2026 - 20:22 NVD
7.5 (HIGH) 1.3 (LOW)
Patch released
Mar 17, 2026 - 20:45 nvd
Patch available
CVE Published
Dec 09, 2025 - 16:18 nvd
HIGH 7.5

DescriptionCVE.org

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 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. This is fixed in version 0.16.0.

Executive ViewAI

Why It Matters

Organizations using matrix-sdk-base face notable risk from CVE-2025-66622 rated CVSS 7.5. Exploitation could compromise the security of affected deployments. A patch is available and should be applied as part of regular vulnerability management.

Business Impact: High
Compensating Controls

Apply vendor patch. If immediate patching is not feasible: (1) Implement network-level access controls to limit exposure; (2) Enable enhanced monitoring and alerting; (3) Apply principle of least privilege.

Threat Intelligence Overview

EPSS Score
0.1%
Top 81% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

6
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +6
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:a:matrix:matrix-rust-sdk:*:*:*:*:*:*:*:*

More in Matrix

View all
CVE-2021-34813 CRITICAL POC
9.8 Jun 16

Matrix libolm before 3.2.3 allows a malicious Matrix homeserver to crash a client (while it is attempting to retrieve an

CVE-2019-19374 CRITICAL POC
9.1 Dec 11

An issue was discovered in core/assets/form/form_question_types/form_question_type_file_upload/form_question_type_file_u

CVE-2019-19373 HIGH POC
7.5 Dec 11

An issue was discovered in Squiz Matrix CMS 5.5.0 prior to 5.5.0.3, 5.5.1 prior to 5.5.1.8, 5.5.2 prior to 5.5.2.4, and

CVE-2025-68667 CRITICAL
9.9 Dec 23

Unauthenticated remote attackers can coerce Conduit-derived Matrix homeservers into cryptographically signing arbitrary

CVE-2023-38690 CRITICAL
9.8 Aug 04

matrix-appservice-irc is a Node.js IRC bridge for Matrix. Rated critical severity (CVSS 9.8), this vulnerability is remo

CVE-2021-44538 CRITICAL
9.8 Dec 14

The olm_session_describe function in Matrix libolm before 3.2.7 is vulnerable to a buffer overflow. Rated critical sever

CVE-2019-18835 CRITICAL
9.8 Nov 08

Matrix Synapse before 1.5.0 mishandles signature checking on some federation APIs. Rated critical severity (CVSS 9.8), t

CVE-2024-45192 MEDIUM POC
5.3 Aug 22

An issue was discovered in Matrix libolm through 3.2.16. Rated medium severity (CVSS 5.3), this vulnerability is remotel

CVE-2024-45191 MEDIUM POC
5.3 Aug 22

An issue was discovered in Matrix libolm through 3.2.16. Rated medium severity (CVSS 5.3), this vulnerability is remotel

CVE-2017-14198 HIGH
8.8 Nov 30

An issue was discovered in Squiz Matrix before 5.3.6.1 and 5.4.x before 5.4.1.3. Rated high severity (CVSS 8.8), this vu

CVE-2023-43656 CRITICAL
9.0 Sep 27

matrix-hookshot is a Matrix bot for connecting to external services like GitHub, GitLab, JIRA, and more. Rated critical

CVE-2022-39203 HIGH
8.8 Sep 13

matrix-appservice-irc is an open source Node.js IRC bridge for Matrix. Rated high severity (CVSS 8.8), this vulnerabilit

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy