<?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>Mon, 12 Oct 2026 13:39:27 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-193911</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-193911</link>
      <description>EUVD-2026-193911</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-193911</guid>
    </item>
    <item>
      <title>fkie_cve-2023-38686</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-38686</link>
      <description>&lt;p&gt;Sydent is an identity server for the Matrix communications protocol. Prior to version 2.5.6, if configured to send emails using TLS, Sydent does not verify SMTP servers&amp;#39; certificates. This makes  Sydent&amp;#39;s emails vulnerable to interception via a man-in-the-middle (MITM) attack. Attackers with privileged access to the network can intercept room invitations and address confirmation emails. This is patched in Sydent 2.5.6. When patching, make sure that Sydent trusts the certificate of the server it is connecting to. This should happen automatically when using properly issued certificates. Those who use self-signed certificates should make sure to copy their Certification Authority certificate, or their self signed certificate if using only one, to the trust store of your operating system. As a workaround, one can ensure Sydent&amp;#39;s emails fail to send by setting the configured SMTP server to a loopback or non-routable address under one&amp;#39;s control which does not have a listening SMTP server.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Sydent is an identity server for the Matrix communications protocol. Prior to version 2.5.6, if configured to send emails using TLS, Sydent does not verify SMTP servers&amp;#39; certificates. This makes  Sydent&amp;#39;s emails vulnerable to interception via a man-in-the-middle (MITM) attack. Attackers with privileged access to the network can intercept room invitations and address confirmation emails. This is patched in Sydent 2.5.6. When patching, make sure that Sydent trusts the certificate of the server it is connecting to. This should happen automatically when using properly issued certificates. Those who use self-signed certificates should make sure to copy their Certification Authority certificate, or their self signed certificate if using only one, to the trust store of your operating system. As a workaround, one can ensure Sydent&amp;#39;s emails fail to send by setting the configured SMTP server to a loopback or non-routable address under one&amp;#39;s control which does not have a listening SMTP server.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-38686</guid>
    </item>
    <item>
      <title>GHSA-p6hw-wm59-3g5g — Sydent does not verify email server certificates</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p6hw-wm59-3g5g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: matrix-sydent&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;If configured to send emails using TLS, Sydent does not verify SMTP servers&amp;#39; certificates. This makes  Sydent&amp;#39;s emails vulnerable to interception via a [man-in-the-middle (MITM) attack](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Attackers with privileged access to the network can intercept room invitations and address confirmation emails.&lt;/p&gt;
&lt;p&gt;CVSS 3.1 overall score: 3.3 - [AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N/CR:L/IR:L/AR:X/MAV:A/MAC:H/MPR:N/MUI:N/MS:C/MC:L/MI:L/MA:N](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N/CR:L/IR:L/AR:X/MAV:A/MAC:H/MPR:N/MUI:N/MS:C/MC:L/MI:L/MA:N&amp;amp;version=3.1)&lt;/p&gt;
&lt;p&gt;_Reported by Martin Schobert, [Pentagrid AG](https://pentagrid.ch/)._&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Sydent can be configured to send emails over a TLS-encrypted socket by setting&lt;/p&gt;
&lt;p&gt;```yaml
email:
    tlsmode: &amp;#34;TLS&amp;#34;  # or the legacy value &amp;#34;SSL&amp;#34;
```&lt;/p&gt;
&lt;p&gt;in its config file. Alternatively it can be configured to use [Opportunistic TLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) by setting&lt;/p&gt;
&lt;p&gt;```yaml
email:
    tlsmode: &amp;#34;STARTTLS&amp;#34;
```&lt;/p&gt;
&lt;p&gt;In both situations, Sydent will encrypt its communication with the SMTP server when sending emails. **In affected versions, Sydent will not verify the destination server&amp;#39;s certificate.**&lt;/p&gt;
&lt;p&gt;### Vulnerability&lt;/p&gt;
&lt;p&gt;Sydent sends email for two purposes:
- to inform a third party that they have been invited to a Matrix room by their email address; and
- to verify that a given Matrix user controls an email address.&lt;/p&gt;
&lt;p&gt;Therefor…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: matrix-sydent&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;If configured to send emails using TLS, Sydent does not verify SMTP servers&amp;#39; certificates. This makes  Sydent&amp;#39;s emails vulnerable to interception via a [man-in-the-middle (MITM) attack](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). Attackers with privileged access to the network can intercept room invitations and address confirmation emails.&lt;/p&gt;
&lt;p&gt;CVSS 3.1 overall score: 3.3 - [AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N/CR:L/IR:L/AR:X/MAV:A/MAC:H/MPR:N/MUI:N/MS:C/MC:L/MI:L/MA:N](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N/CR:L/IR:L/AR:X/MAV:A/MAC:H/MPR:N/MUI:N/MS:C/MC:L/MI:L/MA:N&amp;amp;version=3.1)&lt;/p&gt;
&lt;p&gt;_Reported by Martin Schobert, [Pentagrid AG](https://pentagrid.ch/)._&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Sydent can be configured to send emails over a TLS-encrypted socket by setting&lt;/p&gt;
&lt;p&gt;```yaml
email:
    tlsmode: &amp;#34;TLS&amp;#34;  # or the legacy value &amp;#34;SSL&amp;#34;
```&lt;/p&gt;
&lt;p&gt;in its config file. Alternatively it can be configured to use [Opportunistic TLS](https://en.wikipedia.org/wiki/Opportunistic_TLS) by setting&lt;/p&gt;
&lt;p&gt;```yaml
email:
    tlsmode: &amp;#34;STARTTLS&amp;#34;
```&lt;/p&gt;
&lt;p&gt;In both situations, Sydent will encrypt its communication with the SMTP server when sending emails. **In affected versions, Sydent will not verify the destination server&amp;#39;s certificate.**&lt;/p&gt;
&lt;p&gt;### Vulnerability&lt;/p&gt;
&lt;p&gt;Sydent sends email for two purposes:
- to inform a third party that they have been invited to a Matrix room by their email address; and
- to verify that a given Matrix user controls an email address.&lt;/p&gt;
&lt;p&gt;Therefor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p6hw-wm59-3g5g</guid>
    </item>
    <item>
      <title>gsd-2023-38686</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-38686</link>
      <description>gsd-2023-38686</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-38686</guid>
    </item>
    <item>
      <title>PYSEC-2023-139</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2023-139</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: matrix-sydent&lt;/p&gt;
&lt;p&gt;Sydent is an identity server for the Matrix communications protocol. Prior to version 2.5.6, if configured to send emails using TLS, Sydent does not verify SMTP servers&amp;#39; certificates. This makes  Sydent&amp;#39;s emails vulnerable to interception via a man-in-the-middle (MITM) attack. Attackers with privileged access to the network can intercept room invitations and address confirmation emails. This is patched in Sydent 2.5.6. When patching, make sure that Sydent trusts the certificate of the server it is connecting to. This should happen automatically when using properly issued certificates. Those who use self-signed certificates should make sure to copy their Certification Authority certificate, or their self signed certificate if using only one, to the trust store of your operating system. As a workaround, one can ensure Sydent&amp;#39;s emails fail to send by setting the configured SMTP server to a loopback or non-routable address under one&amp;#39;s control which does not have a listening SMTP server.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: matrix-sydent&lt;/p&gt;
&lt;p&gt;Sydent is an identity server for the Matrix communications protocol. Prior to version 2.5.6, if configured to send emails using TLS, Sydent does not verify SMTP servers&amp;#39; certificates. This makes  Sydent&amp;#39;s emails vulnerable to interception via a man-in-the-middle (MITM) attack. Attackers with privileged access to the network can intercept room invitations and address confirmation emails. This is patched in Sydent 2.5.6. When patching, make sure that Sydent trusts the certificate of the server it is connecting to. This should happen automatically when using properly issued certificates. Those who use self-signed certificates should make sure to copy their Certification Authority certificate, or their self signed certificate if using only one, to the trust store of your operating system. As a workaround, one can ensure Sydent&amp;#39;s emails fail to send by setting the configured SMTP server to a loopback or non-routable address under one&amp;#39;s control which does not have a listening SMTP server.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2023-139</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-38686</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-38686</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: matrix-sydent, Ubuntu:24.04:LTS: matrix-sydent&lt;/p&gt;
&lt;p&gt;Sydent is an identity server for the Matrix communications protocol. Prior to version 2.5.6, if configured to send emails using TLS, Sydent does not verify SMTP servers&amp;#39; certificates. This makes  Sydent&amp;#39;s emails vulnerable to interception via a man-in-the-middle (MITM) attack. Attackers with privileged access to the network can intercept room invitations and address confirmation emails. This is patched in Sydent 2.5.6. When patching, make sure that Sydent trusts the certificate of the server it is connecting to. This should happen automatically when using properly issued certificates. Those who use self-signed certificates should make sure to copy their Certification Authority certificate, or their self signed certificate if using only one, to the trust store of your operating system. As a workaround, one can ensure Sydent&amp;#39;s emails fail to send by setting the configured SMTP server to a loopback or non-routable address under one&amp;#39;s control which does not have a listening SMTP server.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: matrix-sydent, Ubuntu:24.04:LTS: matrix-sydent&lt;/p&gt;
&lt;p&gt;Sydent is an identity server for the Matrix communications protocol. Prior to version 2.5.6, if configured to send emails using TLS, Sydent does not verify SMTP servers&amp;#39; certificates. This makes  Sydent&amp;#39;s emails vulnerable to interception via a man-in-the-middle (MITM) attack. Attackers with privileged access to the network can intercept room invitations and address confirmation emails. This is patched in Sydent 2.5.6. When patching, make sure that Sydent trusts the certificate of the server it is connecting to. This should happen automatically when using properly issued certificates. Those who use self-signed certificates should make sure to copy their Certification Authority certificate, or their self signed certificate if using only one, to the trust store of your operating system. As a workaround, one can ensure Sydent&amp;#39;s emails fail to send by setting the configured SMTP server to a loopback or non-routable address under one&amp;#39;s control which does not have a listening SMTP server.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-38686</guid>
    </item>
  </channel>
</rss>
