<?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-03T17:12:52.698695+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-232550</id>
    <title>EUVD-2026-232550</title>
    <updated>2026-10-03T17:12:52.760379+00:00</updated>
    <content>EUVD-2026-232550</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-232550"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2022-39389</id>
    <title>fkie_cve-2022-39389</title>
    <updated>2026-10-03T17:12:52.760418+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Lightning Network Daemon (lnd) is an implementation of a lightning bitcoin overlay network node. All lnd nodes before version `v0.15.4` are vulnerable to a block parsing bug that can cause a node to enter a degraded state once encountered. In this degraded state, nodes can continue to make payments and forward HTLCs, and close out channels. Opening channels is prohibited, and also on chain transaction events will be undetected. This can cause loss of funds if a CSV expiry is researched during a breach attempt or a CLTV delta expires forgetting the funds in the HTLC. A patch is available in `lnd` version 0.15.4. Users are advised to upgrade. Users unable to upgrade may use the `lncli updatechanpolicy` RPC call to increase their CLTV value to a very high amount or increase their fee policies. This will prevent nodes from routing through your node, meaning that no pending HTLCs can be present.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2022-39389"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hc82-w9v8-83pr</id>
    <title>GHSA-hc82-w9v8-83pr — Witness Block Parsing DoS Vulnerability</title>
    <updated>2026-10-03T17:12:52.760454+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/lightningnetwork/lnd</p>
<p>### Impact</p>
<p>All lnd nodes before version `v0.15.4` are vulnerable to a block parsing bug that can cause a node to enter a degraded state once encountered. In this degraded state, nodes can continue to make payments and forward HTLCs, and close out channels. Opening channels is prohibited, and also on chain transaction events will be undetected.</p>
<p>This can cause loss of funds if a CSV expiry is researched during a breach attempt or a CLTV delta expires forgetting the funds in the HTLC.</p>
<p>### Patches</p>
<p>A patch is available starting with lnd `v0.15.4`.</p>
<p>### Workarounds</p>
<p>Nodes can use the `lncli updatechanpolicy` RPC call to increase their CLTV value to a very high amount or increase their fee policies. This will prevent nodes from routing through your node, meaning that no pending HTLCs can be present.</p>
<p>### References</p>
<p>https://github.com/lightningnetwork/lnd/issues/7096</p>
<p>https://github.com/lightningnetwork/lnd/releases/tag/v0.15.4-beta</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hc82-w9v8-83pr"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2022-39389</id>
    <title>gsd-2022-39389</title>
    <updated>2026-10-03T17:12:52.760492+00:00</updated>
    <content>gsd-2022-39389</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2022-39389"/>
  </entry>
</feed>
