Morning Edition · Sunday, October 25, 2026Published at 1:49 AM EDT · New York
A policy merged on Oct. 22 lets maintainers mark a vulnerability "easily discoverable" and ship fixes for every supported version at once, after AI-assisted scans turned up nearly 5,000 possible flaws across 390 Bitcoin projects.

Bitcoin Core, the reference software that most of the network's nodes run, changed its security disclosure policy after developers found that some vulnerabilities can be found again with very little effort, sometimes with one prompt to an artificial intelligence (AI) model. Under the revision, merged on Oct. 22, reviewers can label a reported flaw "easily discoverable." Maintainers then prepare patches for every supported major version and release them as soon as possible with public advisories, without the usual embargo. The category covers bugs found with simple AI prompts but is not limited to them. All other flaws keep the existing timelines.
Antoine Poinsot, a Bitcoin Core contributor, said large language models make some bugs easier to find, including the quiet code changes developers write to fix a flaw without drawing attention to it. The old practice of a silent patch followed by a late advisory assumed that only a skilled reviewer could reconstruct the bug behind a code change. If a model can read the change and infer the bug, the delay helps attackers more than it helps node operators.
Evidence accumulated throughout the year. The Bitcoin Red Team used frontier and open-weight models to scan 390 Bitcoin-related repositories and produced 4,962 findings, 85 of them critical and 635 high-severity, in about 30 hours. In July, a five-year-old Coldcard firmware flaw that cut seed entropy far below the intended 128 bits led to losses of more than 1,778 bitcoin, and Coinkite, which makes the Coldcard, said AI-assisted review was a plausible way the flaw was found. Outside Bitcoin, Aztec's core contributors said internal AI-assisted auditing found a critical flaw in the Alpha V5 proving system on July 27. Jump Crypto counted 809 reports in its $1 million Firedancer audit contest and said very few were written without an AI agent.
The new policy shifts the exposure risk onto operators. Once an advisory is public, an unpatched node is exposed until its owner upgrades, and crypto.news asked whether operators can update in time.
The same evidence also supports a more pessimistic case for bitcoin's long-term security. Chamath Palihapitiya, the billionaire investor who once promoted bitcoin, said on Peter Diamandis's Moonshots podcast that bitcoin will eventually be hacked and its value will fall to zero, citing advances in AI and quantum computing. Bitcoin Core's answer is procedural. The project now assumes attackers have the same models it has, so it keeps a findable bug private for less time.
Part of a tracked trend
Unaudited Open-Source Crypto Code Surfaces at Scale
Coordinated volunteer and AI-assisted review keeps exposing large backlogs of undiscovered defects in the open-source libraries that wallets, nodes and protocols depend on, so disclosure waves — not novel attacker research — become a recurring driver of emergency patches and incident risk across the ecosystem.
Start a discussion in Townsquare.
More from this edition
What this means
The mechanism is cheaper bug discovery for both attackers and defenders, which removes the value of keeping a findable flaw secret. The exposed parties are slow-upgrading node operators, miners, exchanges and the wallet and Lightning software that reuses Bitcoin Core code, along with open-source libraries that have no full-time maintainers able to ship same-day fixes. The common view treats AI as either an existential threat (Palihapitiya's case) or a non-event. The evidence points to an operational change instead: more frequent advisories and point releases, and a higher cost for running outdated infrastructure. The closest precedent is CVE-2018-17144, the 2018 Bitcoin Core bug that allowed inflation and denial of service. Developers fixed it quickly and disclosed it in stages, and a large share of nodes kept running vulnerable versions for weeks afterward. The desk's read is that within months Bitcoin Core will issue more out-of-cycle releases with same-day advisories, and that hardware-wallet makers and other node implementations will adopt similar fast-track rules. This holds if AI-generated reports keep arriving at the pace the Red Team scan suggests. The read would be wrong if an attacker exploited nodes in the gap between an advisory and the upgrade, because that would push maintainers back toward embargoes.
What to watch
Observations to monitor, not financial advice.
Synthesized from: crypto.news · Polylog editors · Aztec Network · KuCoin News · Analytics Insight · KuCoin Blog · Solana Compass
Comments
0No comments yet.