📰 Bitcoin Core discloses Tor traffic vulnerability affecting configurations of thousands of nodes (According to Bitcoin Core's November 10 disclosure (reported by Bitcoin News; trending topic on the forum, with multiple explanatory posts))

On November 10, Bitcoin Core disclosed three vulnerabilities. The one attracting the most attention is CVE-2025-62860 (medium severity): external connections coming in through Tor could be misidentified as local traffic. If a node was configured with a non-default -whitelist trust range, external connections could gain whitelist privileges and bypass DoS protections and privacy safeguards. Versions prior to 28.3, 29.2, and 30.0 are affected, impacting thousands of mainnet nodes. A fix was released in October 2025, and no active exploitation has been detected by the team. The 29.x series reached end of support on October 27.

What impact does this have?
1. It's protection that's lost, not coins: private keys weren't stolen, and the supply rules haven't changed. What's weakened is the node's immune system, so don't frame a technical vulnerability as “Bitcoin has been hacked.”
2. The real problem is in integration, not the code: when vendors bundled Core with Tor, they also configured a default whitelist. A single default setting determined the security posture of tens of thousands of nodes.
3. The checklist is very specific: node operators should check the version actually running and the -whitelist configuration. Ordinary holders are not directly affected.
Let the news sink in before jumping to conclusions. During windows like this, chasing the news is the easiest way to get hit from both sides.
What do you think: treat this as a short-term sentiment rebound, or wait to see what happens next?
$BTC #BitcoinCoreDisclosesTorTrafficVulnerability
Personal opinions only; this is not investment advice. You are responsible for your own profits and losses.