How severe is GHSA-35g4-qx3c-vjhx?

GHSA-35g4-qx3c-vjhx has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-35g4-qx3c-vjhx?

GHSA-35g4-qx3c-vjhx affects the following packages: matrix-appservice-bridge (npm). Ecosystems affected: npm.

How do I fix GHSA-35g4-qx3c-vjhx?

Update matrix-appservice-bridge to 2.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-35g4-qx3c-vjhx is resolved across your whole dependency graph.

How do I detect GHSA-35g4-qx3c-vjhx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-appservice-bridge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-35g4-qx3c-vjhx if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-35g4-qx3c-vjhx actively exploited in the wild?

No public exploit code has been indexed for GHSA-35g4-qx3c-vjhx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-35g4-qx3c-vjhx?

GHSA-35g4-qx3c-vjhx has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-35g4-qx3c-vjhx?

GHSA-35g4-qx3c-vjhx is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-35g4-qx3c-vjhx published, and has it been updated?

GHSA-35g4-qx3c-vjhx was published on June 21, 2021 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Automatic room upgrade handling can be used maliciously to bridge a room non-consentuallyGHSA-35g4-qx3c-vjhx

MEDIUMFix: matrix-org/matrix-appservice-bridge#330

GHSA-35g4-qx3c-vjhx is a medium-severity (CVSS 6.5) Missing Authentication vulnerability in matrix-appservice-bridge. A fix is available for matrix-appservice-bridge — see the affected versions and patch details below.

Also known asCVE-2021-32659

Published

Jun 21, 2021

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

6other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

matrix-appservice-bridgenpm

3Kdownloads / week

Description

Impact

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 mailcious admin of a bridged room can repoint the traffic to a different room without the new room being aware.

Patches

Versions 2.6.1 and greater are patched.

Workarounds

Disabling the automatic room upgrade handling can be done by removing the roomUpgradeOpts key from the Bridge class options.

References

The issue is patched by https://github.com/matrix-org/matrix-appservice-bridge/pull/330

For more information]

If you have any questions or comments about this advisory, email us at [email protected].

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`matrix-appservice-bridge`	all versions	2.6.1`npm install matrix-appservice-bridge@2.6.1`

Affected Products

1 product · 1 configurations

Application

matrix-appservice-bridgematrix

< 2.6.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-appservice-bridge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update matrix-appservice-bridge to 2.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-35g4-qx3c-vjhx is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact 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 mailcious admin of a bridged room can repoint the traffic to a different room without the new room being aware. ### Patches Versions 2.6.1 and greater are patched. ### Workaroun