Bitcoin Core Discloses Security Flaws That Affected Thousands of Nodes
Bitcoin Core reveals fixed security vulnerabilities
Bitcoin Core developers have revealed details of three security vulnerabilities that were patched in October 2025. The disclosures include a flaw that allowed strangers connecting through Tor to bypass privacy protections on thousands of nodes.
A node is a computer that checks and relays bitcoin transactions and keeps its own copy of the blockchain, which is a shared digital record of all transactions. These flaws were kept quiet for 13 months to allow operators time to update their software before the details were made public.
Key details from the security disclosure
- One medium-severity flaw allowed outside Tor connections to inherit trusted permissions, bypassing spam protections.
- A high-severity bug could stop a mining node from building valid blocks until the software was restarted.
- A third bug allowed malicious connections to stall the processing of new blocks for at least 10 minutes.
- All three issues were addressed in software updates released in October 2025.
How the Tor vulnerability affected nodes
The first vulnerability involved how Bitcoin Core handles trusted connections. Node operators can "whitelist" certain computers, such as those on their own local network, to allow them more traffic than usual. This helps prevent the node from being overwhelmed by too many requests.
When Bitcoin Core was bundled with Tor—a service used to hide internet addresses—the software sometimes mistook incoming Tor connections for local, trusted traffic. This meant thousands of nodes were accidentally granting full trusted permissions to strangers connecting over the Tor network. This issue was reported in September 2025 and rated as medium severity.
Mining risks and block processing delays
A high-severity bug affected nodes that were used for mining. This flaw was related to the mempool, which is the list of pending payments waiting to be added to the blockchain. Under certain conditions involving competing versions of the blockchain, a node could fail its own validity checks. This would prevent the miner from creating valid blocks until they manually restarted the system.
Another medium-severity bug allowed an attacker to stall a node's processing of new blocks. By controlling specific connections used for fast block relay, a malicious user could repeat this disruption indefinitely, keeping the node from staying up to date with the rest of the network.
Why the developers waited a year to disclose
Bitcoin Core typically follows a policy of waiting 13 months before publishing the full details of medium- and high-severity bugs. This delay is intended to ensure that enough node operators have installed the fix, making it harder for attackers to exploit the vulnerability once the details are public.
While developers recently updated their rules to disclose AI-discoverable bugs faster, these specific flaws followed the traditional, longer timeline. The last affected software series reached the end of its support period in late October 2026, leading to the formal disclosure this week.