<?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>Tue, 06 Oct 2026 19:31:06 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-31512</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-31512</link>
      <description>EUVD-2026-31512</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-31512</guid>
    </item>
    <item>
      <title>fkie_cve-2021-41171</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-41171</link>
      <description>&lt;p&gt;eLabFTW is an open source electronic lab notebook manager for research teams. In versions of eLabFTW before 4.1.0, it allows attackers to bypass a brute-force protection mechanism by using many different forged PHPSESSID values in HTTP Cookie header. This issue has been addressed by implementing brute force login protection, as recommended by Owasp with Device Cookies. This mechanism will not impact users and will effectively thwart any brute-force attempts at guessing passwords. The only correct way to address this is to upgrade to version 4.1.0. Adding rate limitation upstream of the eLabFTW service is of course a valid option, with or without upgrading.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;eLabFTW is an open source electronic lab notebook manager for research teams. In versions of eLabFTW before 4.1.0, it allows attackers to bypass a brute-force protection mechanism by using many different forged PHPSESSID values in HTTP Cookie header. This issue has been addressed by implementing brute force login protection, as recommended by Owasp with Device Cookies. This mechanism will not impact users and will effectively thwart any brute-force attempts at guessing passwords. The only correct way to address this is to upgrade to version 4.1.0. Adding rate limitation upstream of the eLabFTW service is of course a valid option, with or without upgrading.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-41171</guid>
    </item>
    <item>
      <title>gsd-2021-41171</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-41171</link>
      <description>gsd-2021-41171</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-41171</guid>
    </item>
  </channel>
</rss>
