#BitcoinCoreDisclosesTorTrafficVulnerability Don’t panic over the Tor bug news. The real story is “delay,” not “danger.” 🧅
Bitcoin Core disclosed 3 patched vulnerabilities. “Thousands” of reachable mainnet nodes were whitelisting incoming Tor connections, which removed some DoS limits and privacy protections. Nodes that didn’t have this non-default setting were not affected. (theblock)
The truth about the timeline:
✅ The fix was included in Bitcoin Core 30.0 (Oct 10, 2025) and 29.2 (Oct 14, 2025). The last vulnerable version reached end-of-life on Oct 27, 2026.
✅ The project ships the fix first, then shares the vulnerability details later.
⚠️ This is not an issue with consensus rules. The risk was to node privacy and reliability, not to coins or the Bitcoin protocol. (theblock) (cryptovalleyjournal)
My analysis: This is a textbook example of “responsible disclosure.” First the patch, then time for users to upgrade, and only then a public advisory. That’s the power of open source: a bug is found, fixed, and later everything is made public. But there’s a lesson here too: operators running old node versions should upgrade now.
(Not financial advice, DYOR.)
Do you run your own node, or do you trust an exchange/custodian? Why? 👇
#BitcoinCoreDisclosesTorTrafficVulnerability #Bitcoin❗ #Tor #BitcoinCore
Bitcoin Core disclosed 3 patched vulnerabilities. “Thousands” of reachable mainnet nodes were whitelisting incoming Tor connections, which removed some DoS limits and privacy protections. Nodes that didn’t have this non-default setting were not affected. (theblock)
The truth about the timeline:
✅ The fix was included in Bitcoin Core 30.0 (Oct 10, 2025) and 29.2 (Oct 14, 2025). The last vulnerable version reached end-of-life on Oct 27, 2026.
✅ The project ships the fix first, then shares the vulnerability details later.
⚠️ This is not an issue with consensus rules. The risk was to node privacy and reliability, not to coins or the Bitcoin protocol. (theblock) (cryptovalleyjournal)
My analysis: This is a textbook example of “responsible disclosure.” First the patch, then time for users to upgrade, and only then a public advisory. That’s the power of open source: a bug is found, fixed, and later everything is made public. But there’s a lesson here too: operators running old node versions should upgrade now.
(Not financial advice, DYOR.)
Do you run your own node, or do you trust an exchange/custodian? Why? 👇
#BitcoinCoreDisclosesTorTrafficVulnerability #Bitcoin❗ #Tor #BitcoinCore