Thousands of nodes once inherited “trusted” status because Tor traffic was treated as local traffic.
Bitcoin News posted on X that the vulnerability disclosed by Bitcoin Core affected setups where providers bundled Bitcoin Core with Tor: incoming Tor traffic was treated as local traffic, so nodes with whitelist settings enabled relaxed spam and privacy restrictions for external nodes. The fix was released in October 2025, and details were disclosed two weeks after support for the 29.x series ended.
· Nodes without whitelist settings enabled were unaffected; no related attacks have been reported so far.
· Another high-severity vulnerability could prevent mining nodes from building valid blocks until they were restarted.
Does your node have whitelist settings enabled?
#BTC
Bitcoin News posted on X that the vulnerability disclosed by Bitcoin Core affected setups where providers bundled Bitcoin Core with Tor: incoming Tor traffic was treated as local traffic, so nodes with whitelist settings enabled relaxed spam and privacy restrictions for external nodes. The fix was released in October 2025, and details were disclosed two weeks after support for the 29.x series ended.
· Nodes without whitelist settings enabled were unaffected; no related attacks have been reported so far.
· Another high-severity vulnerability could prevent mining nodes from building valid blocks until they were restarted.
Does your node have whitelist settings enabled?
#BTC
