Bitcoin Core reveals bug that made thousands of nodes trust any stranger on Tor
- Published
- Updated
Bitcoin Core disclosed a Tor-related vulnerability that gave incoming Tor connections trusted permissions on thousands of nodes. The issue was identified as CVE-2025-62860, and the disclosure was published on Nov. 10.
Key claims & sources
What it means
Bitcoin Core is the reference software for running a Bitcoin node, and Tor is often used to hide network identity when nodes connect. A vulnerability in that path matters because it affects how Bitcoin Core handles inbound traffic from hidden-service connections. The Nov. 10 disclosure names the bug as CVE-2025-62860 and places it inside the software layer that operators use to reach the Bitcoin network privately.
Operators who run Bitcoin Core behind Tor may need to review how their nodes treat incoming connections and whether those connections receive trust they should not have. The immediate concern is not trading or price, but whether node behavior matches the operator’s security assumptions. If a node accepts more trust than intended, the operator may need to change how it configures privacy and access controls.
The case sits at the point where privacy tooling and network hardening meet, and Bitcoin’s design depends on both being usable at the same time. A Tor flaw inside Bitcoin Core raises the uncomfortable trade-off between making nodes harder to monitor and making them easier to misuse. That tension matters because Bitcoin infrastructure is supposed to be permissionless, yet node software still has to decide whom to trust and when.
Bitcoin Core has not settled every practical question yet, including which deployments were exposed and what specific configuration changes operators should make next. The disclosure names the bug, but the remaining work is to map its reach across the installed base and confirm how node operators should update their setups. The next concrete checkpoint is whether follow-up guidance or releases narrow the affected surface for Tor-connected nodes.
Market reaction i
Bitcoin barely moved in the 4 hours after the first headline, after falling 0.3% in the 2 hours before.
47 prices, one every 30 minutes · The move was larger before the first headline than after: an observation, not an explanation. The market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.