CVE-2025-54315VulnerabilityPublished 2 Oct 2025

CVE-2025-54315: Matrix specification · Improper Enforcement of a Single, Unique Action

Affects Matrix specificationSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:L

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Matrix Matrix specification	Affected =0	Fixed in–

AI-suggested

European organizations should proactively monitor updates from the Matrix specification maintainers and apply any forthcoming patches or version upgrades that address this vulnerability. In the absence of official patches, organizations can implement strict validation and filtering rules on their Matrix servers to detect and block duplicate or conflicting create events. Deploying enhanced logging and anomaly detection focused on room creation events can help identify exploitation attempts early. Network segmentation and access controls should be enforced to limit exposure of Matrix servers to untrusted networks. Organizations should also review and tighten permissions related to room creation and management to reduce the risk of unauthorized actions. Engaging with the Matrix community to stay informed about best practices and interim mitigations is advisable. Finally, conducting internal audits of Matrix room configurations and federated connections can help identify potential risks arising from this vulnerability.

Description

The Matrix specification before 1.16 (i.e., with a room version before 12) lacks create event uniqueness.

Impact

For European organizations relying on Matrix-based communication platforms, this vulnerability could undermine the integrity and reliability of internal and external communications. Attackers exploiting this flaw could create conflicting or unauthorized rooms, potentially leading to confusion, misinformation, or unauthorized access to communication channels. This could disrupt business operations, especially in sectors where secure and reliable messaging is critical, such as government, finance, healthcare, and critical infrastructure. The scope change in the CVSS vector suggests that the vulnerability could affect multiple components or services interacting with the Matrix protocol, increasing the risk of cascading failures or broader service disruptions. Although confidentiality is not directly impacted, the integrity and availability issues could indirectly lead to data leakage or operational downtime. Given the decentralized nature of Matrix, organizations using federated servers or bridging to other communication platforms may face amplified risks if the vulnerability is exploited in interconnected environments.

CWE-837Improper Enforcement of a Single, Unique Action (opens in a new tab)
Base weakness
The product requires that an actor should only be able to perform an action once, or to have only one unique action, but the product does not enforce or improperly enforces this restriction.
OWASP ASVS 4.0.3
V11.1.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Oct 2025, 18:42 UTC

WeaknessesCWE-837

Technical details

References

Community reviews

Related threats