<?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>Thu, 08 Oct 2026 16:41:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-216518</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-216518</link>
      <description>EUVD-2026-216518</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-216518</guid>
    </item>
    <item>
      <title>fkie_cve-2023-32682</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-32682</link>
      <description>&lt;p&gt;Synapse is a Matrix protocol homeserver written in Python with the Twisted framework. In affected versions it may be possible for a deactivated user to login when using uncommon configurations. This only applies if any of the following are true: 1. JSON Web Tokens are enabled for login via the `jwt_config.enabled` configuration setting. 2. The local password database is enabled via the `password_config.enabled` and `password_config.localdb_enabled` configuration settings *and* a user&amp;#39;s password is updated via an admin API after a user is deactivated. Note that the local password database is enabled by default, but it is uncommon to set a user&amp;#39;s password after they&amp;#39;ve been deactivated. Installations that are configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected. If not using JSON Web Tokens, ensure that deactivated users do not have a password set. This issue has been addressed in version 1.85.0. Users are advised to upgrade.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Synapse is a Matrix protocol homeserver written in Python with the Twisted framework. In affected versions it may be possible for a deactivated user to login when using uncommon configurations. This only applies if any of the following are true: 1. JSON Web Tokens are enabled for login via the `jwt_config.enabled` configuration setting. 2. The local password database is enabled via the `password_config.enabled` and `password_config.localdb_enabled` configuration settings *and* a user&amp;#39;s password is updated via an admin API after a user is deactivated. Note that the local password database is enabled by default, but it is uncommon to set a user&amp;#39;s password after they&amp;#39;ve been deactivated. Installations that are configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected. If not using JSON Web Tokens, ensure that deactivated users do not have a password set. This issue has been addressed in version 1.85.0. Users are advised to upgrade.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-32682</guid>
    </item>
    <item>
      <title>GHSA-26c5-ppr8-f33p — Synapse has improper checks for deactivated users during login</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-26c5-ppr8-f33p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: matrix-synapse&lt;/p&gt;
&lt;p&gt;### Impact
It may be possible for a deactivated user to login when using uncommon configurations.&lt;/p&gt;
&lt;p&gt;This only applies if any of the following are true:&lt;/p&gt;
&lt;p&gt;* [JSON Web Tokens are enabled for login](https://matrix-org.github.io/synapse/latest/jwt.html) via the `jwt_config.enabled` configuration setting
* The [local password database is enabled](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#password_config) via the `password_config.enabled` and `password_config.localdb_enabled` configuration settings *and* a user&amp;#39;s password is [updated via an admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#create-or-modify-account) after a user is deactivated.&lt;/p&gt;
&lt;p&gt;**Note that the local password database is enabled by default**, but it is uncommon to set a user&amp;#39;s password after they&amp;#39;ve been deactivated.&lt;/p&gt;
&lt;p&gt;Installations that are configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;* If using JSON Web Token logins: #15624
* For other users: #15634&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If not using JSON Web Tokens, ensure that deactivated users do not have a password set. This list of users can be queried from PostgreSQL:&lt;/p&gt;
&lt;p&gt;```sql
SELECT name FROM users WHERE password_hash IS NOT NULL AND deactivated = 1;
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: matrix-synapse&lt;/p&gt;
&lt;p&gt;### Impact
It may be possible for a deactivated user to login when using uncommon configurations.&lt;/p&gt;
&lt;p&gt;This only applies if any of the following are true:&lt;/p&gt;
&lt;p&gt;* [JSON Web Tokens are enabled for login](https://matrix-org.github.io/synapse/latest/jwt.html) via the `jwt_config.enabled` configuration setting
* The [local password database is enabled](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#password_config) via the `password_config.enabled` and `password_config.localdb_enabled` configuration settings *and* a user&amp;#39;s password is [updated via an admin API](https://matrix-org.github.io/synapse/latest/admin_api/user_admin_api.html#create-or-modify-account) after a user is deactivated.&lt;/p&gt;
&lt;p&gt;**Note that the local password database is enabled by default**, but it is uncommon to set a user&amp;#39;s password after they&amp;#39;ve been deactivated.&lt;/p&gt;
&lt;p&gt;Installations that are configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;* If using JSON Web Token logins: #15624
* For other users: #15634&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;If not using JSON Web Tokens, ensure that deactivated users do not have a password set. This list of users can be queried from PostgreSQL:&lt;/p&gt;
&lt;p&gt;```sql
SELECT name FROM users WHERE password_hash IS NOT NULL AND deactivated = 1;
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-26c5-ppr8-f33p</guid>
    </item>
    <item>
      <title>gsd-2023-32682</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-32682</link>
      <description>gsd-2023-32682</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-32682</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:13039-1 — matrix-synapse-1.85.2-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:13039-1</link>
      <description>&lt;p&gt;matrix-synapse-1.85.2-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;matrix-synapse-1.85.2-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:13039-1</guid>
    </item>
    <item>
      <title>PYSEC-2023-84</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2023-84</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: matrix-synapse&lt;/p&gt;
&lt;p&gt;Synapse is a Matrix protocol homeserver written in Python with the Twisted framework. In affected versions it may be possible for a deactivated user to login when using uncommon configurations. This only applies if any of the following are true: 1. JSON Web Tokens are enabled for login via the `jwt_config.enabled` configuration setting. 2. The local password database is enabled via the `password_config.enabled` and `password_config.localdb_enabled` configuration settings *and* a user&amp;#39;s password is updated via an admin API after a user is deactivated. Note that the local password database is enabled by default, but it is uncommon to set a user&amp;#39;s password after they&amp;#39;ve been deactivated. Installations that are configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected. If not using JSON Web Tokens, ensure that deactivated users do not have a password set. This issue has been addressed in version 1.85.0. Users are advised to upgrade.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: matrix-synapse&lt;/p&gt;
&lt;p&gt;Synapse is a Matrix protocol homeserver written in Python with the Twisted framework. In affected versions it may be possible for a deactivated user to login when using uncommon configurations. This only applies if any of the following are true: 1. JSON Web Tokens are enabled for login via the `jwt_config.enabled` configuration setting. 2. The local password database is enabled via the `password_config.enabled` and `password_config.localdb_enabled` configuration settings *and* a user&amp;#39;s password is updated via an admin API after a user is deactivated. Note that the local password database is enabled by default, but it is uncommon to set a user&amp;#39;s password after they&amp;#39;ve been deactivated. Installations that are configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected. If not using JSON Web Tokens, ensure that deactivated users do not have a password set. This issue has been addressed in version 1.85.0. Users are advised to upgrade.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2023-84</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-32682</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-32682</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: matrix-synapse, Ubuntu:Pro:20.04:LTS: matrix-synapse, Ubuntu:22.04:LTS: matrix-synapse&lt;/p&gt;
&lt;p&gt;Synapse is a Matrix protocol homeserver written in Python with the Twisted framework. In affected versions it may be possible for a deactivated user to login when using uncommon configurations. This only applies if any of the following are true: 1. JSON Web Tokens are enabled for login via the `jwt_config.enabled` configuration setting. 2. The local password database is enabled via the `password_config.enabled` and `password_config.localdb_enabled` configuration settings *and* a user&amp;#39;s password is updated via an admin API after a user is deactivated. Note that the local password database is enabled by default, but it is uncommon to set a user&amp;#39;s password after they&amp;#39;ve been deactivated. Installations that are configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected. If not using JSON Web Tokens, ensure that deactivated users do not have a password set. This issue has been addressed in version 1.85.0. Users are advised to upgrade.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: matrix-synapse, Ubuntu:Pro:20.04:LTS: matrix-synapse, Ubuntu:22.04:LTS: matrix-synapse&lt;/p&gt;
&lt;p&gt;Synapse is a Matrix protocol homeserver written in Python with the Twisted framework. In affected versions it may be possible for a deactivated user to login when using uncommon configurations. This only applies if any of the following are true: 1. JSON Web Tokens are enabled for login via the `jwt_config.enabled` configuration setting. 2. The local password database is enabled via the `password_config.enabled` and `password_config.localdb_enabled` configuration settings *and* a user&amp;#39;s password is updated via an admin API after a user is deactivated. Note that the local password database is enabled by default, but it is uncommon to set a user&amp;#39;s password after they&amp;#39;ve been deactivated. Installations that are configured to only allow login via Single Sign-On (SSO) via CAS, SAML or OpenID Connect (OIDC); or via an external password provider (e.g. LDAP) are not affected. If not using JSON Web Tokens, ensure that deactivated users do not have a password set. This issue has been addressed in version 1.85.0. Users are advised to upgrade.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-32682</guid>
    </item>
  </channel>
</rss>
