<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 17 Oct 2026 21:56:51 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-28047</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-28047</link>
      <description>EUVD-2026-28047</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-28047</guid>
    </item>
    <item>
      <title>fkie_cve-2021-32659</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-32659</link>
      <description>&lt;p&gt;Matrix-appservice-bridge is the bridging service for the Matrix communication program&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Matrix-appservice-bridge is the bridging service for the Matrix communication program&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-32659</guid>
    </item>
    <item>
      <title>GHSA-35g4-qx3c-vjhx — Automatic room upgrade handling can be used maliciously to bridge a room non-consentually</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-35g4-qx3c-vjhx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: matrix-appservice-bridge&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Versions 2.6.1 and greater are patched.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Disabling the automatic room upgrade handling can be done by removing the `roomUpgradeOpts` key from the `Bridge` class options.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;The issue is patched by https://github.com/matrix-org/matrix-appservice-bridge/pull/330&lt;/p&gt;
&lt;p&gt;### For more information]&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, email us at security@matrix.org.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: matrix-appservice-bridge&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Versions 2.6.1 and greater are patched.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Disabling the automatic room upgrade handling can be done by removing the `roomUpgradeOpts` key from the `Bridge` class options.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;The issue is patched by https://github.com/matrix-org/matrix-appservice-bridge/pull/330&lt;/p&gt;
&lt;p&gt;### For more information]&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, email us at security@matrix.org.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-35g4-qx3c-vjhx</guid>
    </item>
    <item>
      <title>gsd-2021-32659</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-32659</link>
      <description>gsd-2021-32659</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-32659</guid>
    </item>
  </channel>
</rss>
