<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T06:25:55.756685+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-232640</id>
    <title>EUVD-2026-232640</title>
    <updated>2026-10-08T06:25:55.759534+00:00</updated>
    <content>EUVD-2026-232640</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-232640"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-36071</id>
    <title>fkie_cve-2022-36071</title>
    <updated>2026-10-08T06:25:55.759574+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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'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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-36071"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-54qx-8p8w-xhg8</id>
    <title>GHSA-54qx-8p8w-xhg8 — SFTPGo vulnerable to recovery codes abuse</title>
    <updated>2026-10-08T06:25:55.759614+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/drakkan/sftpgo/v2</p>
<p>### Impact</p>
<p>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.</p>
<p>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'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.</p>
<p>### Patches</p>
<p>Fixed in v2.3.4.
Recovery codes can now only be generated after enabling two-factor authentication and are deleted after disabling it.</p>
<p>### Workarounds</p>
<p>Regenerate recovery codes after enabling two-factor authentication.</p>
<p>### References</p>
<p>https://github.com/drakkan/sftpgo/issues/965</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-54qx-8p8w-xhg8"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-36071</id>
    <title>gsd-2022-36071</title>
    <updated>2026-10-08T06:25:55.759652+00:00</updated>
    <content>gsd-2022-36071</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-36071"/>
  </entry>
</feed>
