Bitcoin Core developer Antoine Poinsot said on the Bitcoin development mailing list that the project is changing its security vulnerability disclosure policy.
Poinsot said vulnerabilities were often kept private for extended periods under the previous approach so users could upgrade before technical details were published. That practice also created a tradeoff: fixes could not be backported to older versions, leaving users to wait for the next major release.
Easy-to-find bugs will be patched quickly across maintained releases
Poinsot said large language models have made some vulnerabilities much easier to rediscover, leaving limited security benefit in continuing to delay fixes.
Under the new policy, vulnerabilities classified as easy to find will be fixed as soon as possible in all maintained major versions, and a security advisory will be published at the same time. The category covers flaws that require very little effort to identify, including cases where a simple LLM prompt can surface the issue.
Other flaws still follow a severity-based disclosure schedule
Vulnerabilities outside that category will continue to follow the existing timeline based on severity.
- Low-severity vulnerabilities will be disclosed two weeks after the major release that includes the fix.
- Medium- and high-severity vulnerabilities will be disclosed two weeks after the last affected version reaches end of life, which Poinsot said is typically one year after the new major release containing the fix.
- Critical vulnerabilities fall outside the standard policy and may require ad hoc procedures.
Researcher reaction and recent context
Bitcoin ecosystem security researcher Luke de Wolf said he had not agreed with Poinsot’s earlier security strategy, but viewed the latest update as a good adjustment.
In August this year, the volunteer-run Bitcoin Red Team reported nearly 5,000 potential issues across 390 projects. At the time, only about one-fifth had been reproduced.
That same month, Core Lightning developers, after receiving multiple AI-generated vulnerability reports, urged operators to upgrade or take nodes offline while withholding technical details for two weeks.


