<?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>Sun, 04 Oct 2026 04:43:16 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-46282</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-46282</link>
      <description>EUVD-2026-46282</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-46282</guid>
    </item>
    <item>
      <title>fkie_cve-2020-26896</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-26896</link>
      <description>&lt;p&gt;Prior to 0.11.0-beta, LND (Lightning Network Daemon) had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn&amp;#39;t verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount collision with an invoice, the preimage for an expected payment was instead released. A malicious peer could have deliberately intercepted an HTLC intended for the victim node, probed the preimage through a colluding relayed HTLC, and stolen the intercepted HTLC. The impact is a loss of funds in certain situations, and a weakening of the victim&amp;#39;s receiver privacy.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Prior to 0.11.0-beta, LND (Lightning Network Daemon) had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn&amp;#39;t verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount collision with an invoice, the preimage for an expected payment was instead released. A malicious peer could have deliberately intercepted an HTLC intended for the victim node, probed the preimage through a colluding relayed HTLC, and stolen the intercepted HTLC. The impact is a loss of funds in certain situations, and a weakening of the victim&amp;#39;s receiver privacy.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-26896</guid>
    </item>
    <item>
      <title>gsd-2020-26896</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-26896</link>
      <description>gsd-2020-26896</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-26896</guid>
    </item>
  </channel>
</rss>
