<?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>Wed, 07 Oct 2026 07:44:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-256560</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-256560</link>
      <description>EUVD-2026-256560</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-256560</guid>
    </item>
    <item>
      <title>fkie_cve-2025-56800</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-56800</link>
      <description>&lt;p&gt;Reolink desktop application 8.18.12 contains a vulnerability in its local authentication mechanism. The application implements lock screen password logic entirely on the client side using JavaScript within an Electron resource file. Because the password is stored and returned via a modifiable JavaScript property(a.settingsManager.lockScreenPassword), an attacker can patch the return value to bypass authentication. NOTE: this is disputed by the Supplier because the lock-screen bypass would only occur if the local user modified his own instance of the application.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Reolink desktop application 8.18.12 contains a vulnerability in its local authentication mechanism. The application implements lock screen password logic entirely on the client side using JavaScript within an Electron resource file. Because the password is stored and returned via a modifiable JavaScript property(a.settingsManager.lockScreenPassword), an attacker can patch the return value to bypass authentication. NOTE: this is disputed by the Supplier because the lock-screen bypass would only occur if the local user modified his own instance of the application.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-56800</guid>
    </item>
    <item>
      <title>GHSA-6wpr-v4mr-q5hf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6wpr-v4mr-q5hf</link>
      <description>&lt;p&gt;Reolink desktop application 8.18.12 contains a vulnerability in its local authentication mechanism. The application implements lock screen password logic entirely on the client side using JavaScript within an Electron resource file. Because the password is stored and returned via a modifiable JavaScript property(a.settingsManager.lockScreenPassword), an attacker can patch the return value to bypass authentication.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Reolink desktop application 8.18.12 contains a vulnerability in its local authentication mechanism. The application implements lock screen password logic entirely on the client side using JavaScript within an Electron resource file. Because the password is stored and returned via a modifiable JavaScript property(a.settingsManager.lockScreenPassword), an attacker can patch the return value to bypass authentication.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6wpr-v4mr-q5hf</guid>
    </item>
  </channel>
</rss>
