<?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 06:25:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-232640</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-232640</link>
      <description>EUVD-2026-232640</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-232640</guid>
    </item>
    <item>
      <title>fkie_cve-2022-36071</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-36071</link>
      <description>&lt;p&gt;SFTPGo is configurable SFTP server with optional HTTP/S, FTP/S and WebDAV support. SFTPGo WebAdmin and WebClient support login using TOTP (Time-based One Time Passwords) as a secondary authentication factor. Because TOTPs are often configured on mobile devices that can be lost, stolen or damaged, SFTPGo also supports recovery codes. These are a set of one time use codes that can be used instead of the TOTP. In SFTPGo versions from version 2.2.0 to 2.3.3 recovery codes can be generated before enabling two-factor authentication. An attacker who knows the user&amp;#39;s password could potentially generate some recovery codes and then bypass two-factor authentication after it is enabled on the account at a later time. This issue has been fixed in version 2.3.4. Recovery codes can now only be generated after enabling two-factor authentication and are deleted after disabling it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SFTPGo is configurable SFTP server with optional HTTP/S, FTP/S and WebDAV support. SFTPGo WebAdmin and WebClient support login using TOTP (Time-based One Time Passwords) as a secondary authentication factor. Because TOTPs are often configured on mobile devices that can be lost, stolen or damaged, SFTPGo also supports recovery codes. These are a set of one time use codes that can be used instead of the TOTP. In SFTPGo versions from version 2.2.0 to 2.3.3 recovery codes can be generated before enabling two-factor authentication. An attacker who knows the user&amp;#39;s password could potentially generate some recovery codes and then bypass two-factor authentication after it is enabled on the account at a later time. This issue has been fixed in version 2.3.4. Recovery codes can now only be generated after enabling two-factor authentication and are deleted after disabling it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-36071</guid>
    </item>
    <item>
      <title>GHSA-54qx-8p8w-xhg8 — SFTPGo vulnerable to recovery codes abuse</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-54qx-8p8w-xhg8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/drakkan/sftpgo/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;SFTPGo WebAdmin and WebClient support login using TOTP (Time-based One Time Passwords) as a seconday authentication factor. Because TOTPs are often configured on mobile devices that can be lost, stolen or damaged, SFTPGo also supports recovery codes. These are a set of one time use codes that can be used instead of the TOTP.&lt;/p&gt;
&lt;p&gt;In SFTPGo versions from v2.2.0 to v2.3.3 recovery codes can be generated before enabling two-factor authentication.
An attacker who knows the user&amp;#39;s password could potentially generate some recovery codes and then bypass two-factor authentication after it is enabled on the account at a later time.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in v2.3.4.
Recovery codes can now only be generated after enabling two-factor authentication and are deleted after disabling it.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Regenerate recovery codes after enabling two-factor authentication.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;https://github.com/drakkan/sftpgo/issues/965&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/drakkan/sftpgo/v2&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;SFTPGo WebAdmin and WebClient support login using TOTP (Time-based One Time Passwords) as a seconday authentication factor. Because TOTPs are often configured on mobile devices that can be lost, stolen or damaged, SFTPGo also supports recovery codes. These are a set of one time use codes that can be used instead of the TOTP.&lt;/p&gt;
&lt;p&gt;In SFTPGo versions from v2.2.0 to v2.3.3 recovery codes can be generated before enabling two-factor authentication.
An attacker who knows the user&amp;#39;s password could potentially generate some recovery codes and then bypass two-factor authentication after it is enabled on the account at a later time.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in v2.3.4.
Recovery codes can now only be generated after enabling two-factor authentication and are deleted after disabling it.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Regenerate recovery codes after enabling two-factor authentication.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;https://github.com/drakkan/sftpgo/issues/965&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-54qx-8p8w-xhg8</guid>
    </item>
    <item>
      <title>gsd-2022-36071</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-36071</link>
      <description>gsd-2022-36071</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-36071</guid>
    </item>
  </channel>
</rss>
