News linked to both this project and an event.
Bitcoin Core disclosed a moderate-severity vulnerability discovered by an AI tool that allows attackers to temporarily block nodes from processing messages by repeatedly broadcasting transactions.
Bitcoin News posted on X platform that Bitcoin Core has disclosed a vulnerability: when service providers bundle Bitcoin Core with Tor, incoming Tor traffic is treated as local traffic, causing nodes with whitelist settings enabled to relax spam and privacy restrictions for external nodes, allowing them to inherit "trusted" status across thousands of nodes. The fix was released in October 2025, and Bitcoin Core only disclosed the details two weeks after ending support for the 29.x series. Another high-severity vulnerability could prevent mining nodes from building valid blocks until restarted; no related attacks have been reported, and nodes without whitelist settings enabled are not affected.
Bitcoin Core disclosed a fixed Tor connection whitelist vulnerability where nodes under specific configurations may grant trusted status to inbound connections.
Odaily reports: Bitcoin News posted on X that Bitcoin Core has disclosed a high-risk vulnerability where affected miners may be unable to produce valid blocks after a chain reorganization occurs. The vulnerability is tracked as CVE-2025-62861 and affects Bitcoin Core versions 28.0 through 28.2 and 29.0 through 29.1. A fixed version was released in October 2025, and details of the vulnerability were made public today. Security researcher Niklas Goegge discovered the vulnerability.
Bitcoin Core disclosed a medium-severity vulnerability that allows malicious nodes to cause block processing on affected nodes to stall under specific conditions. A fix was released in 2025.
Odaily reports: b14g has released a post-mortem report on the security incident of October 31, 2026. It states that the attacker exploited a compatibility flaw between its staking contract and the Core network's native staking contract, initiating 99 zero-amount (0 CORE) withdrawal requests across 91 staking orders in a single transaction, resulting in the theft of approximately 97.05 million CORE. The attack did not involve any private key leak, nor did the attacker modify or deploy any new b14g contract code. BTC staked through b14g was unaffected and remains locked on the Bitcoin chain.Regarding fund recovery, approximately 68.15 million CORE (about 70.2% of the total stolen) was recovered on November 2 through a Core hard fork, and another approximately 12 million CORE has reportedly been frozen by trading platforms. As for user compensation, b14g plans to return the recovered CORE within the next 5 to 7 days in proportion to the original balances of each affected order, with the remaining losses to be repaid through 50% of future Core staking business revenue, claimable by affected users on a weekly basis.
Cory Fields proposes implementing a collateral and challenge mechanism for quantum-vulnerable Bitcoin to increase the cost of stealing coins.
According to Fields' proposal, an attacker attempting to steal 1 BTC would need to provide an additional 1 BTC as collateral from their quantum-secure wallet. Both funds would be locked for a waiting period, such as 30 days. Before a quantum attack becomes feasible, the original owner could create a quantum-secure "mine" containing a hidden proof of ownership. If the thief later attempts to transfer the vulnerable coins, both the stolen BTC and the thief's collateral will be locked. During the waiting period, the owner can reveal the proof to reclaim their BTC and claim the thief's collateral as a penalty. The thief cannot determine which addresses have traps set before deploying funds.
Odaily Report: Marc Zeller, founder of the Aave Chan Initiative (ACI), posted on X stating that the Aave protocol is fine.The Binance hacker injected 60 million USDT into the protocol within just 3 minutes and borrowed 19,762 wETH (approximately $44.9 million), at which point Tether had not yet frozen the address, nor had the Aave Guardian frozen the Aave V3 Core pool's reserves (this operation occurred 46 minutes later).However, USDT is backed by real dollars, and from the protocol's perspective, although this position is the proceeds of crime, it is overcollateralized — with a health factor of 1.04, holding $59.9 million in collateral against $44.9 million in debt.Of course, the protocol now has a large borrower with little incentive to repay the loan, but the liquidation mechanism will still operate as usual. If the ETH price rises above approximately $2,365 (+4%), the position will be liquidated just like any other position.Currently, the Aave V3 Core pool's total wETH reserves stand at 2.16 million wETH, and the hacker's debt accounts for "only" 0.9% of that, so Aave does not need to take any special action against the hacker. There are currently 345,000 wETH available (capital utilization rate of 81.6%), so if wETH depositors wish to withdraw, liquidity is fully sufficient. There is no reason or need for a bank run to occur.This situation is far less alarming than the Kelp hacker incident (which involved zero-value collateral). In theory, a governance proposal could be passed to force liquidation of the hacker by upgrading the pool (if the USDT liquidation threshold were lowered, it would affect all USDT depositors), but there is no practical benefit to doing so, as the normal liquidation mechanism can easily absorb this debt.
Bitcoin News posted on X that Bitcoin Core has discovered 3 new vulnerabilities, one of which could allow an attacker to remotely crash nodes. This vulnerability can affect nodes running Windows, macOS, or BSD by exhausting memory, while Linux nodes are not affected by this attack; another vulnerability can gradually exhaust node memory, and a third may corrupt blockchain undo data.
Odaily reports: Bitcoin Core developers have merged a security policy adjustment. For vulnerabilities that can be easily discovered or rediscovered through simple large language model (LLM) prompts, the previous long-term confidential disclosure mechanism will no longer be used. The new rules allow developers to mark such issues as "easy to find" during vulnerability classification, then backport fixes to all still-supported versions and release them as soon as possible through minor version updates, along with a security advisory and some vulnerability details.Previously, Bitcoin Core scheduled disclosure based on vulnerability severity, with medium- and high-risk vulnerabilities usually only made public after the affected versions stopped being maintained. This adjustment stems from AI tools lowering the threshold for vulnerability discovery: in July this year, a Bitcoin Red Team composed of 16 developers used AI models to scan about 390 Bitcoin-related projects and recorded 4,962 findings in one day, of which 85 were listed as critical issues. Developers noted that continuing to extend the confidentiality period for such vulnerabilities can no longer effectively prevent attacks and instead delays the release of fixed versions; however, the new rules also mean that fixes may lack longer testing time. Currently, no vulnerability has been officially marked as falling into the "easy to find" category under the new rules. (CoinDesk)
According to Cointelegraph, Bitcoin Core developer Antoine Poinsot stated on Thursday on the bitcoin-dev mailing list that large language models (LLMs) have made certain software vulnerabilities extremely easy to rediscover. Maintaining long-term secrecy is already of limited value and instead delays the release of patched versions, prompting the team to update its vulnerability disclosure policy. The new policy dictates that "easily discoverable" vulnerabilities, which can be identified with minimal cost such as through simple LLM prompts, will be patched as soon as possible across all supported major versions, alongside the simultaneous release of security advisories. Other vulnerabilities will continue to be disclosed based on severity: low-severity vulnerabilities will be disclosed two weeks after the release of the major version containing the fix; medium-to-high-severity vulnerabilities will be disclosed two weeks after the end-of-life (EOL) of the last affected version, typically around one year after the patch release; critical vulnerabilities will be handled through a dedicated process.
Bitcoin Core has adjusted its security vulnerability disclosure policy, defining easily discoverable vulnerabilities as those that can be found through simple large language model prompts, and will release fixes as soon as possible across all major versions still under maintenance, while publishing security advisories.Bitcoin Core developer Antoine Poinsot stated that in the past, vulnerabilities were typically kept confidential during a longer disclosure embargo period to allow users to upgrade, but large language models have lowered the threshold for rediscovering certain vulnerabilities, limiting the protective value of delayed fixes.Low-severity vulnerabilities will be disclosed two weeks after the major version containing the fix is released; medium- and high-severity vulnerabilities will be disclosed two weeks after the affected version reaches end of life, typically about one year after the fix enters a new version. Critical vulnerabilities are not subject to the standard policy and will be handled through ad hoc procedures.In August, the volunteer organization Bitcoin Red Team reported nearly 5,000 potential issues across 390 projects, with about one-fifth having been reproduced at the time. Core Lightning developers that same month asked node operators to upgrade or take nodes offline, and delayed disclosure of technical details for two weeks. (Cointelegraph)
On-chain investigator ZachXBT stated that FreedomXMR (FXMR), a centralized money laundering service that appeared on Hyperliquid Core (HL Core) in August 2026, had over 87% of its incoming funds directly linked to illegal activities. A review of historical inflows exceeding $10,000 revealed that over $20 million could be directly traced to ransomware, security exploits, malware, and social engineering incidents, involving multiple theft cases such as the DCENT Wallet, Fetch.ai, Axelar, and Gamdom.
Odaily reports, according to Bitcoin News monitoring, Core Lightning stated that attackers are targeting nodes still running version 26.06.7 and earlier. The 26.06.8 patch released on September 22 fixes a channel closure issue that could jeopardize funds, as well as vulnerabilities that cause crashes and memory exhaustion. The project has not yet disclosed the name of the vulnerability used by attackers, nor has it reported any stolen funds. Node operators who have not yet upgraded are becoming attack targets.
the Core Lightning team, which develops the Bitcoin Lightning Network node software, is warning node operators running version 26.06.7 or earlier to upgrade to the latest version as soon as possible. The team said it has received reports of attackers targeting unpatched nodes, but did not disclose the vulnerability exploited by the attackers or the potential impact.Core Lightning said on September 16 that it was investigating an issue that could affect experimental features and user funds, and on September 22 released version 26.06.8 to fix the vulnerability and update the software. This announcement did not state whether the previously reported attacks were related to the vulnerability fixed in this version. (Cointelegraph)
Odaily reports: Bitcoin News posted on X that Core Lightning is urging node operators to immediately disable experimental features, as developers are investigating a vulnerability that could put channel funds at risk. This is Core Lightning's second warning within a few weeks, following an August patch and the release of the 26.06.7 upgrade after a series of AI-generated CVE reports. Core Lightning has not yet disclosed how the experimental feature could be exploited.
Odaily reports: Bitcoin News posted on X platform that Bitcoin Core developer Niklas Gögge warned that recent AI-driven vulnerability scanning is changing the Bitcoin security landscape. Large language models have significantly reduced the cost of vulnerability discovery, and attackers may be able to find catastrophic vulnerabilities with only a few hundred dollars in computing costs. For Bitcoin Core, Project Loupe, Bitcoin Red Team, and individual contributors have generated over 1,000 reports, but so far no high-risk or critical vulnerabilities have been found. Gögge stated that relying on stronger models to find vulnerabilities before attackers do is not a sustainable security strategy. Developers should build testing infrastructure through automated testing, fuzzing, and property-based testing that can prevent entire classes of vulnerabilities in advance. Key components of Bitcoin Core have cumulatively completed over 100 years of CPU fuzzing and decades of Bitcoin node network simulation.
According to CoinDesk, Bitcoin Core 32.0 entered its final testing phase on September 14, with its official release scheduled for October 10. This update adds a transaction fee estimator based on real-time mempool status, enabling fee estimates to be lowered more quickly once network congestion subsides. It also enables multi-threaded parallel reading of transaction data to speed up node blockchain synchronization, defaulting to 8 threads. Security-wise, it resolves a wallet naming vulnerability on non-Windows systems since version 24.0 that allowed attackers to execute arbitrary commands on the node host via a specially crafted wallet name. Additionally, it patches an out-of-memory vulnerability in the newly added built-in web server; testing indicates that 16 unauthenticated connections can spike node memory usage from 46MB to roughly 3GB in approximately one minute. This update does not include any changes to Bitcoin's consensus rules.
Odaily News: Bitcoin Core 32.0 entered its final testing phase on September 14, with the official version planned for release on October 10.This version will improve fee estimation, speed up block processing, and make PSBT version 2 the default option for multiple wallet commands, without changing Bitcoin's consensus rules.Developers also fixed a command execution vulnerability affecting certain wallet configurations, as well as a memory exhaustion vulnerability in the new web server. (CoinDesk)