Security & Protocols
Two Days to Fix, Six Months to Tell: Core Ends Secrecy on Readily Found Bugs
As machine review lowers the cost of rediscovery toward zero, maintaining a year-long embargo no longer protects operators—it merely withholds the patch.
For over twenty years, coordinated vulnerability disclosure operated on a settled economic premise: finding a subtle flaw in complex software was costly and slow, so maintainers could safely withhold details for months while node operators quietly patched. That assumption collapsed this week under the weight of machine-assisted code analysis, prompting Bitcoin Core to rewrite its disclosure doctrine.
The turning point was laid bare by Roger in an exhaustive review of a severe Core Lightning flaw [s588]. Reported on 23 April 2026, the vulnerability allowed an attacker controlling a funded 2-of-2 multisig output to crash any peer by broadcasting a channel announcement naming the same node as both endpoints. Because the code wrote the message to disk before validating unique IDs, an unhandled duplicate-assertion tripped on every startup, permanently trapping the daemon in a crash loop. While a one-line ordering fix was merged the very next day, 182 days elapsed before public disclosure arrived on 24 October.
That six-month silence reflected legacy practice, but maintainers recognized the calculus has inverted. In a policy amendment authored by Antoine Poinsot and merged on 22 October, Bitcoin Core formally abandoned embargoes for flaws that can be discovered with minimal effort: The public disclosure timeline will depend on whether we classify a reported vulnerability as easily discoverable. This classification applies to vulnerabilities that can be discovered with minimal effort, such as through a simple LLM prompt.
For this category, backported point releases and public advisories will ship simultaneously.
The shift acknowledges reality: when an artificial model can scan hundreds of repositories and uncover thousands of anomalies in an afternoon, an embargo denies defenders the fix while leaving attackers free to rediscover the hole. As Roger observed, The difference between attacker and defender is not who can find the bug. It is who already has the patch.
Defense can no longer lean on secrets; it must rely entirely on velocity and rigorous boundary validation.