LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32659: Automatic room upgrade handling can be used maliciously to bridge a room non-consentually

Matrix-appservice-bridge is the bridging service for the Matrix communication program's application services. In versions 2.6.0 and earlier, if a bridge has room upgrade handling turned on in the configuration (the `roomUpgradeOpts` key when instantiating a new `Bridge` instance.), any `m.room.tombstone` event it encounters will be used to unbridge the current room and bridge into the target room. However, the target room `m.room.create` event is not checked to verify if the `predecessor` field contains the previous room. This means that any malicious admin of a bridged room can repoint the traffic to a different room without the new room being aware. Versions 2.6.1 and greater are patched. As a workaround, disabling the automatic room upgrade handling can be done by removing the `roomUpgradeOpts` key from the `Bridge` class options.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A vulnerable Matrix bridge can be tricked by a malicious admin of an existing bridged room into redirecting bridged traffic to another room without that target room's consent or awareness. The main business risk is confidentiality: messages intended for one bridged room may be exposed to an unintended room.

Executive priority

Treat as a targeted confidentiality risk for Matrix bridge operators, not a broad internet-wide emergency. Patch or disable automatic room upgrades promptly where bridges carry sensitive communications, because the flaw can redirect messages without consent once a bridged-room admin is malicious or compromised.

Technical view

matrix-appservice-bridge versions 2.6.0 and earlier mishandle automatic room upgrades when roomUpgradeOpts is enabled. The bridge accepts an m.room.tombstone target without verifying the target room's m.room.create predecessor points back to the prior room. A malicious bridged-room admin can repoint bridge traffic. Version 2.6.1 patched this.

Likely exposure

Exposure is limited to deployments using matrix-org matrix-appservice-bridge before 2.6.1 with automatic room upgrade handling enabled. Organizations not running this bridge, already on 2.6.1 or later, or without roomUpgradeOpts enabled are not described as affected by the supplied sources.

Exploitation context

The source bundle does not show known active exploitation, and KEV status is false. Abuse requires low privileges: administrative control of a bridged room. The impact is high confidentiality exposure, with no integrity or availability impact stated in the CVSS vector.

Researcher notes

The key validation point is configuration-dependent exposure: vulnerable version plus roomUpgradeOpts. Sources identify the missing predecessor check and the vendor patch, but do not provide evidence of exploitation in the wild. Avoid assuming affected downstream services unless they use matrix-appservice-bridge in the vulnerable configuration.

Mitigation direction

  • Upgrade matrix-appservice-bridge to version 2.6.1 or later.
  • If immediate upgrade is not possible, remove roomUpgradeOpts to disable automatic room upgrade handling.
  • Review vendor advisory and release notes for deployment-specific guidance.
  • Prioritize bridges carrying sensitive or regulated conversations.

Validation and detection

  • Inventory deployed matrix-appservice-bridge versions and identify any below 2.6.1.
  • Inspect bridge configuration for roomUpgradeOpts automatic upgrade handling.
  • Confirm patched deployments run version 2.6.1 or later.
  • Review bridged-room administration rights for unnecessary privileged users.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32659 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-32659Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
matrix-orgmatrix-appservice-bridge< 2.6.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.