<?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>Sat, 03 Oct 2026 05:02:35 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-07878</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-07878</link>
      <description>bdu:2026-07878</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-07878</guid>
    </item>
    <item>
      <title>EUVD-2026-260173</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-260173</link>
      <description>EUVD-2026-260173</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-260173</guid>
    </item>
    <item>
      <title>fkie_cve-2025-8850</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-8850</link>
      <description>&lt;p&gt;In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows users to disable 2FA without requiring a valid OTP or backup code, bypassing the intended verification process. This vulnerability occurs because the backend does not properly validate the OTP or backup code when the API endpoint &amp;#39;/api/auth/2fa/disable&amp;#39; is directly accessed. This flaw can be exploited by authenticated users to weaken the security of their own accounts, although it does not lead to full account compromise.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows users to disable 2FA without requiring a valid OTP or backup code, bypassing the intended verification process. This vulnerability occurs because the backend does not properly validate the OTP or backup code when the API endpoint &amp;#39;/api/auth/2fa/disable&amp;#39; is directly accessed. This flaw can be exploited by authenticated users to weaken the security of their own accounts, although it does not lead to full account compromise.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-8850</guid>
    </item>
    <item>
      <title>GHSA-x5w7-gch7-xjf6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x5w7-gch7-xjf6</link>
      <description>&lt;p&gt;In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows users to disable 2FA without requiring a valid OTP or backup code, bypassing the intended verification process. This vulnerability occurs because the backend does not properly validate the OTP or backup code when the API endpoint &amp;#39;/api/auth/2fa/disable&amp;#39; is directly accessed. This flaw can be exploited by authenticated users to weaken the security of their own accounts, although it does not lead to full account compromise.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows users to disable 2FA without requiring a valid OTP or backup code, bypassing the intended verification process. This vulnerability occurs because the backend does not properly validate the OTP or backup code when the API endpoint &amp;#39;/api/auth/2fa/disable&amp;#39; is directly accessed. This flaw can be exploited by authenticated users to weaken the security of their own accounts, although it does not lead to full account compromise.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x5w7-gch7-xjf6</guid>
    </item>
  </channel>
</rss>
