https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 14:16:44 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-136566 EUVD-2026-136566 https://cve.radiocsirt.org/vuln/euvd-2026-136566 https://cve.radiocsirt.org/vuln/fkie_cve-2024-34478 <p>btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of funds.</p> <p>btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of funds.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-34478 https://cve.radiocsirt.org/vuln/ghsa-3jgf-r68h-xfqm <p><strong>Affected:</strong> Go: github.com/btcsuite/btcd</p> <p>btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of funds.</p> <p><strong>Affected:</strong> Go: github.com/btcsuite/btcd</p> <p>btcd before 0.24.0 does not correctly implement the consensus rules outlined in BIP 68 and BIP 112, making it susceptible to consensus failures. Specifically, it uses the transaction version as a signed integer when it is supposed to be treated as unsigned. There can be a chain split and loss of funds.</p> https://cve.radiocsirt.org/vuln/ghsa-3jgf-r68h-xfqm