Thousands of Bitcoin nodes were trusted by default because they connected via Tor.
In a November 10 security disclosure, Bitcoin Core confirmed the vulnerability, tracked as CVE-2025-62860: inbound connections from Tor were automatically granted whitelist privileges, disabling some protections against spam and privacy leaks. Crypto.news reported the disclosure, and developers have released a fix.
· The issue affects thousands of nodes, not the entire network; the broader permissions mean anti-abuse checks for these connections are skipped.
· The report does not say whether the vulnerability has been exploited, nor does it provide a complete list of affected versions.
Does your node run behind Tor or connect directly to the public internet?
In a November 10 security disclosure, Bitcoin Core confirmed the vulnerability, tracked as CVE-2025-62860: inbound connections from Tor were automatically granted whitelist privileges, disabling some protections against spam and privacy leaks. Crypto.news reported the disclosure, and developers have released a fix.
· The issue affects thousands of nodes, not the entire network; the broader permissions mean anti-abuse checks for these connections are skipped.
· The report does not say whether the vulnerability has been exploited, nor does it provide a complete list of affected versions.
Does your node run behind Tor or connect directly to the public internet?
