Bitcoin Core disclosed a configuration vulnerability on Nov. 10 that gave incoming Tor connections trusted status on thousands of reachable Bitcoin mainnet nodes. Bitcoin Core assigned CVE-2025-62860 a medium-severity rating. Vulnerable releases were affected only when a non-default -whitelist configuration included the IP address of the node's Tor daemon. Nodes without that setting were unaffected.
Bitcoin Core receives the Tor daemon's IP address for an incoming Tor connection, rather than the remote peer's actual network address. The Tor daemon handles Tor connections and usually operates on the node's machine or local network. Affected configurations compared the daemon's address with an IP range designated as trusted. Incoming Tor connections received whitelist permissions whenever that range included the daemon's address. The intermediary's local address could not establish whether a remote peer deserved trust.
The -whitelist setting removes various restrictions against denial-of-service behavior and mitigations against privacy leaks. The disclosed privileges concern network-peer exemptions and do not establish wallet access or coin theft. Bitcoin Core said popular vendors packaged the node software with Tor and a whitelist range that included the daemon's address. Bitcoin Core said some client software also required whitelisting and frequently operated alongside Tor. Bitcoin Core attributed the exposure of thousands of reachable mainnet nodes to these configurations, which trusted all incoming Tor connections. That finding describes historical exposure rather than the number of nodes that remain vulnerable today.
Martin Zumsande and Antoine Poinsot reported the vulnerability in September 2025. The patch was merged on Sept. 17. The patch prevented address-based whitelist permissions from applying to incoming onion connections, which conceal remote network addresses. Bitcoin Core versions 30.0, 29.2 and 28.3 included the fix when those releases became available in October 2025. Every version starting with 30.0 includes the fix, as do subsequent minor releases in the fixed 28.x and 29.x branches.
However, the minimum versions containing the fix are distinct from the versions operators should adopt now. Bitcoin Core currently maintains the 30.x, 31.x and 32.x branches. The 28.x and 29.x branches have reached end of life. Bitcoin Core recommends using the latest maintenance release within the newest major version an operator can adopt. Bitcoin Core's download page identifies 32.1 as the latest release as of Nov. 11. Operators using packaged node software should verify the Bitcoin Core version actually running and check whether the configured whitelist range includes the Tor daemon's address.
Bitcoin Core Discloses Tor Whitelist Vulnerability Affecting Thousands of Nodes
CryptoSlateShare
Bitcoin Core released a vulnerability news update on Nov. 10, addressing a flaw (CVE-2025-62860) that allowed Tor connections to gain trusted status on thousands of nodes. The issue came from a non-default -whitelist setting including the Tor daemon’s IP. Bitcoin news reports that the flaw was reported in September 2025 and patched on Sept. 17. Fixes are in versions 30.0, 29.2, and 28.3, with 32.x now recommended.
Source:Show original
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.

