# AI forces Bitcoin Core to change its security policy

> Bitcoin Core speeds up fixes for bugs that AI can easily discover and removes the usual confidentiality deadlines
> By Covadonga Fernandez · Bitcoin · 2026-10-23

AI is forcing a change in how Bitcoin's software is protected, judging by the update to Bitcoin Core's security policy. Developers will speed up the release of fixes for bugs that can be easily discovered, including through a simple AI query, instead of keeping them under the usual confidentiality deadlines.

The reasoning is that if a tool makes it possible to find a bug with little effort, an attacker can also use it to discover it. Under those circumstances, keeping the problem secret for months offers less protection and delays a solution reaching users. That is how Antoine Poinsot, author of the proposal approved yesterday, October 22, explains it. The change affects the management of vulnerabilities in Bitcoin Core, the software used to run nodes that verify Bitcoin transactions and blocks.

## AI reduces the usefulness of keeping bugs secret

Poinsot notes that the project has seen an increase in reports of vulnerabilities that can be easily discovered or rediscovered. He attributes much of that increase to large language models, which reduce the effort needed to locate certain classes of bugs or identify fixes made quietly.

**[Goodbye to 80 bytes: Bitcoin Core frees OP\_RETURN for unlimited data](https://observatorioblockchain.com/bitcoin/adios-a-los-80-bytes-bitcoin-core-libera-op_return-sin-limites/)**

Until now, the policy of [Bitcoin Core](https://github.com/bitcoin/bitcoin) favored prolonged confidentiality periods to give users time to update the software before disclosing the details. According to the developer, that approach generally prevented fixes from being adapted to earlier versions and meant solutions were only available with the next major release.

For bugs that are easy to find, the developers believe that wait no longer offers a sufficient advantage, since others can discover the same bug while users still lack a fixed version.

## Fixes for all maintained versions

The new policy introduces the possibility of classifying a vulnerability as easily detectable during its assessment. The category includes bugs that can be located with a simple AI query, though it can also apply to problems discovered by other methods.

In these cases, Bitcoin Core will publish a corrective update as soon as possible for each major version that is still maintained. At the same time it will issue a security notice, without applying the confidentiality deadlines envisaged for other vulnerabilities. This will allow fixes to also reach those using earlier versions still covered by the project's maintenance.

Speed poses a delicate balance, since disclosing helps users protect themselves but can also give attackers clues before everyone has updated. Bitcoin Core's decision stems from the fact that, when a bug is easy to rediscover, keeping it reserved offers less protection.

## Other bugs keep their deadlines

The update does not eliminate confidentiality periods for all vulnerabilities. Minor bugs that do not fall into the new category will be disclosed two weeks after the release of a major version that includes the fix. Medium and high severity ones will be reported two weeks after support ends for the last affected version, roughly a year after the first fixed major version is published. Critical problems will still require a specific response.
