Bitcoin Core Discloses Tor Vulnerability Affecting Thousands of Nodes

iconCoinDesk
Share
AI summary iconSummary
Bitcoin Core issued a security advisory on November 12, 2026, revealing a flaw that allowed Tor connections to bypass spam and privacy protections on thousands of nodes. The vulnerability, reported in September 2025, gave trusted permissions to external Tor users if the local Tor address was in a trusted range. The flaw was fixed in October 2025, but the advisory was released two weeks after support for the last affected release ended. Two other vulnerabilities were also disclosed, including a high-severity issue related to blockchain version handling and a medium-severity flaw allowing block processing interruptions. The incident highlights the importance of security in both Proof of Work (PoW) and Proof of Stake (PoS) networks.

Bitcoin Core issued a security advisory on Tuesday about a flaw that gave outside Tor connections trusted permissions on thousands of bitcoin nodes. Those permissions allowed strangers to bypass spam and privacy protections. Developers disclosed three vulnerabilities on Tuesday, all corrected in software releases issued in October 2025, about 13 months before the detailed disclosures.

Bitcoin nodes verify and relay transactions and retain copies of the blockchain. Nodes normally restrict traffic from connected computers to resist attempts to overwhelm the nodes. Bitcoin Core's whitelist setting eases some restrictions for trusted connections, including computers on an operator's local network.

The Tor flaw arose when providers packaged Bitcoin Core with Tor, which conceals internet addresses. Outside connections through Tor appeared to originate from the local Tor software. Outside visitors received trusted permissions if the local Tor software's address belonged to a trusted range. The advisory said thousands of reachable mainnet nodes consequently gave whitelist permissions to every incoming Tor connection. Nodes without the whitelist setting enabled were not affected.

Martin Zumsande and Antoine Poinsot reported the Tor flaw in September 2025. Bitcoin Core classified the vulnerability as medium severity. Poinsot privately notified affected software providers on September 19, 2025. The advisory published Tuesday did not identify those providers. The corrective code had been publicly available on GitHub since September 2025, with a title explicitly stating that incoming Tor connections should not receive whitelist permissions.

The high-severity vulnerability concerned the handling of competing blockchain versions. Transactions from discarded blocks can reenter the mempool, the list of pending payments, when the network abandons a blockchain version. A rule added in Bitcoin Core 28.0 could delete a restored transaction without deleting transactions dependent on that transaction. An affected node would attempt to construct blocks containing transactions with missing inputs, which the node's validity checks would reject. An affected mining node could not produce valid block templates until the operator restarted the node. Niklas Goegge reported the vulnerability on September 26, 2025. The advisory reported no attacks.

The remaining vulnerability, classified as medium severity, allowed a malicious connection to interrupt a node's processing of new blocks for 10 minutes. An attacker controlling all three connections chosen for fast block relay could prolong the interruption indefinitely by repeating the attack. The advisory identified a configuration that processes only blocks as an additional way to cause repeated interruptions.

Bitcoin Core normally releases details about medium- and high-severity vulnerabilities two weeks after support ends for the final affected release. The waiting period gives operators an opportunity to install fixes before technical explanations become public. Support for 29.x, the last affected release series, ended on October 27. Tuesday fell two weeks after that date.

Developers revised the disclosure policy in October for vulnerabilities that are easy to rediscover, including with a simple prompt to an AI model. Under the revised policy, those vulnerabilities receive a corrected release and an advisory as quickly as possible. Tuesday's disclosures used the longer disclosure schedule.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.