
A new medium severity advisory has been posted: https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/
Post summary
The tweet announces a new medium severity advisory for CVE-2025-62860, indicating a vendor advisory has been published.
Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE
| Date | Total | Labels |
|---|
| 2026-11-10 | 4 | Disclosure1General1Patch2 |
| 2026-11-11 | 10 | Disclosure3General2Patch3 |
| 2026-11-12 | 6 | Disclosure1Patch4 |
| 2026-11-13 | 3 | Patch1 |

A new medium severity advisory has been posted: https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/
Post summary
The tweet announces a new medium severity advisory for CVE-2025-62860, indicating a vendor advisory has been published.

🚨 Bitcoin Core fixed a Tor-related vulnerability that could weaken node privacy and DoS protection. On November 11, Bitcoin Core disclosed a medium-severity vulnerability tracked as CVE-2025-62860. The bug affected nodes using optional whitelist settings when their configured IP ranges included Tor proxy servers. ⚠️ Why it matters: - Thousands of mainnet nodes may have mistakenly whitelisted incoming Tor connections. - This could bypass certain denial-of-service protections. - It could also weaken privacy protections intended for node operators. 🛠️ Patch status: - Bitcoin Core 30.0 and 29.2 included the fix in October 2025. - Two additional vulnerabilities involving block processing and block template creation by mining nodes were also disclosed. This was a configuration-dependent vulnerability, not evidence that Bitcoin's entire network or all Tor users were compromised. Bitcoin's security model keeps evolving. Even the network's privacy layer needs regular maintenance. 🔐 Are node operators keeping their software updated, or just hoping nobody finds the next bug?

Bitcoin Core discloses Tor whitelist vulnerability affecting thousands of nodes Bitcoin Core has published an advisory for CVE-2025-62860. The medium-severity vulnerability caused inbound Tor connections to incorrectly receive -whitelist permissions. What the issue was Bitcoin Core saw the IP address of an incoming Tor peer as the address of the local Tor daemon. If that address fell within the range set by the -whitelist option, any external Tor peer received trusted-node privileges. This lifted some DoS limits and weakened certain privacy protections. According to the developers, the vulnerability affected thousands of reachable mainnet nodes because popular Bitcoin Core + Tor bundles came with a preconfigured -whitelist. Nodes that did not enable the -whitelist option (it is not enabled by default) were not affected. Fix and disclosure The bug was fixed back in October 2025 in versions 28.3, 29.2, and 30.0. Public disclosure took place on November 10, 2026 — roughly 13 months after the patch was released, in line with the project's disclosure policy. Node operators running Tor are advised to verify they are on a patched version (or later) and ensure their whitelist configuration does not cover the Tor daemon's address.

For free subscribers: Jensen Huang, Statistics Hiding Decline, Noble Losers, Chinese Analysis of America, Why Most Charity Doesn't Work and more! For paid subscribers: Tracey, Testnet5, CVE-2025-62860, pi402, Emergency Exit, Plea for L2 Development, Blockstream's Custody Solution, Deutsche Bank Launches Bitcoin Custody and more! #Bitcoin Tech Talk #527 https://jimmysong.substack.com/p/bitcoin-tech-talk-527

https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/ Look at the actual timeline: Apr 28, 2025 — compact-blocks bug reported Sept 12, 2025 — Tor whitelist bug reported by Zumsande and Poinsot Sept 17, 2025 — fix merged Oct 10–20, 2025 — fixes shipped in 30.0, 29.2, 28.3 Oct 27, 2026 — 29.x reaches end of life Nov 10, 2026 — details published So the public description landed roughly 13 months after the patches

Bitcoin Core披露三项漏洞:受影响节点应升级 热度:★★★★☆ @bitcoincoreorg 公布三项已经修复的安全问题。 CVE-2025-62861影响Bitcoin Core 28.0–28.2和29.0–29.1。在特定重组及内存池状态下,矿工可能无法继续生成区块模板,通常需要重启才能恢复。 另外两项问题分别涉及compact block处理停滞,以及配置-whitelist时,Tor入站连接可能被错误加入白名单。默认没有使用该参数的节点不受后一项配置问题影响。 相关修复已进入28.3、29.2和30.0。节点、矿池及基础设施运营者应升级到对应分支的修复版本,并检查白名单配置。仅使用普通钱包、没有运行Bitcoin Core节点的用户无需迁移资产。 信息源: https://bitcoincore.org/en/security-advisories/ https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62861/ https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62859/ https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/ #Bitcoin #BitcoinCore #Node #Mining
Post summary
The text reports that Bitcoin Core disclosed three fixed security vulnerabilities and recommends upgrading affected nodes, miners, and infrastructure operators to patched versions. No active exploitation or PoC was indicated.

Thousands of reachable Bitcoin Core nodes trusted every inbound Tor connection, Bitcoin Core says. Tor peers arrive with the daemon's local address, which matched the -whitelist range some vendors set. Fixed Oct 2025; disclosed Nov 10, 2026. https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/

@Lightlike1 https://antoinep.com/posts/cve-2025-62860/
Post summary
The text simply shares a link to a blog post about CVE-2025-62860 without providing specific indicators such as PoC, exploit code, patch details, or active exploitation claims.

Milhares de nós Bitcoin tratavam qualquer estranho vindo pelo Tor como se fosse da casa. O Bitcoin Core divulgou em 10/11 a CVE-2025-62860. Quem rodava Core junto com Tor e com -whitelist cobrindo o IP do daemon dava a peers de fora as permissões de peer confiável: menos limite anti-DoS, menos proteção de privacidade. A correção saiu em outubro de 2025. O detalhe só veio a público 13 meses depois, de propósito, pra dar tempo de atualizar. O furo não estava no Tor nem no Bitcoin. Estava no pacote "plug and play" que configurou tudo por você. https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/

Thousands of Bitcoin nodes treated every incoming Tor connection as a trusted peer. Bitcoin Core disclosed the bug yesterday (CVE-2025-62860). Some node bundles set -whitelist to an IP range that covered their own Tor daemon. Every Tor peer arrives from that address, so all of them got past DoS limits and privacy protections. It was about network limits, not keys or coins. Fixed in 28.3, 29.2 and 30.0 in October 2025. Running a node from a bundle? Check your version and your -whitelist line. Plan ₿
Post summary
Bitcoin Core disclosed CVE-2025-62860, where Tor connections were improperly trusted due to a -whitelist misconfiguration, and fixed versions 28.3, 29.2, and 30.0 were released in October 2025.

比特币节点有个bug能让矿工出不了块,修完一年多才公开细节 Bitcoin Core 11/10 一次披露3个漏洞(1个高危、2个中危),补丁早在2025年10月就发了: 高危 CVE-2025-62861:影响 28.0–28.2、29.0–29.1。链重组时 TRUC(v3) 交易的"兄弟驱逐"规则误触发,mempool 状态错乱,矿工节点生成不了有效区块模板,只能重启恢复 中危 CVE-2025-62860:开了 -whitelist 且IP段覆盖Tor代理的节点,会把Tor入站连接全当白名单,官方说主网有数千个可达节点这样配置 中危 CVE-2025-62859:恶意节点利用压缩区块的 witness 篡改拖住区块处理,每次最长10分钟,特定条件下可无限重复 为什么现在才说:最后一个受影响的 29.x 分支 10/27 停止维护,按披露政策才公开。公告没提到资金被盗或共识出问题。 跑节点/挖矿的查一下版本,30.0+ 或 29.2+ 三个都修了 BTC 现价约 $74.4K,24h +2%,恐贪指数 29(Fear) DYOR 自己判断 #BTC #BitcoinCore #Crypto
Post summary
Bitcoin Core disclosed three vulnerabilities (one high, two medium) patched in October 2025, with details on mempool corruption blocking miners and DoS via witness tampering. Fixed versions are 30.0+ and 29.2+; no active exploitation or PoC mentioned.

Bitcoin Core disclosed CVE-2025-62860: nodes that trusted an address range with -whitelist could end up trusting every incoming Tor peer, because Tor hands those connections over from a local address. Fixed in 30.0, 29.2 and 28.3 in Oct 2025. #Bitcoin https://t.co/Dm4oWQr9X9

2つめは、-whitelistオプションを使用しているノードで、Torのインバウンド接続ピアが誤ってホワイトリストに登録されてしまう問題。 https://bitcoincore.org/ja/2026/11/10/disclose-cve-2025-62860/
Post summary
The text discloses a vulnerability (CVE-2025-62860) in Bitcoin Core involving an access control logic error where Tor inbound peers are incorrectly whitelisted when the -whitelist option is used, linking to the official vendor disclosure page.

Update to version 30.0 now to fix three Bitcoin Core vulnerabilities, including CVE-2025-62861, CVE-2025-62860, and CVE-2025-62859 affecting nodes. #BitcoinCore #Bitcoin #BlockchainSecurity #Cybersecurity #InfoSec https://securityonline.info/bitcoin-core-vulnerabilities-cve-2025-62861-patched/
Post summary
The tweet urges users to update to Bitcoin Core version 30.0 to patch three CVEs (CVE-2025-62861, CVE-2025-62860, CVE-2025-62859).

2/25 Run a Bitcoin node? Check its software. An old Bitcoin Core flaw gave outsiders trusted permissions in some Tor privacy setups. It required a non-default trusted-address setting; nodes without it were unaffected. https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/ https://t.co/gPtM1R1Zcp

2/25 Run a Bitcoin node? Check its software. An old Bitcoin Core flaw gave outsiders trusted permissions in some Tor privacy setups. It required a non-default trusted-address setting; nodes without it were unaffected. https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/ https://t.co/TKBdx5i0NQ

Bitcoin Core disclosed a Tor bug (CVE-2025-62860): some nodes treated every inbound Tor connection as a trusted peer. It was patched in October 2025. Running an older node over Tor? Update it.
Post summary
The text reports that Bitcoin Core disclosed and fixed a Tor-related trust flaw (CVE-2025-62860) in which some nodes treated every inbound Tor connection as a trusted peer, patched in October 2025. Its main takeaway is the remediation call to update older Tor-running nodes, with no PoC, exploit tooling, or evidence of in-the-wild abuse cited.

Sources: Bitcoin Core advisory (10 Nov) https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/ , The Block https://www.theblock.co/news/ecosystems/2026-11-11-bitcoin-core-discloses-three-patched-security-flaws-including-high-severity-mining-bug-437862 , CryptoSlate https://cryptoslate.com/thousands-of-bitcoin-nodes-gave-anonymous-strangers-a-pass-around-security-limits/
Post summary
The snippet only lists source URLs for a Bitcoin Core advisory and related articles, without providing any concrete details about the CVE, PoC, exploit, active exploitation, patch, or false‑positive status.

4/ – Dar trato de “peer de confianza” a cualquiera que entrara por Tor. Según el aviso oficial, afectó a miles de nodos por cómo los configuraban algunos proveedores y programas que se conectan a ellos. (Fuente: https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/) 👇
Post summary
The text discloses technical details of CVE-2025-62860, explaining that Bitcoin Core treated Tor connections as trusted peers, impacting thousands of nodes due to configuration practices, and references the official Bitcoin Core advisory.

🛡️ Bitcoin Core flags Tor flaw CVE-2025-62860 enabling trusted Tor access on thousands of nodes, weakening spam protections and privacy. Patch out. #crypto #cryptonews #Bitcoin #Tor #privacy 🛡️ https://t.co/bMHgOE5Rkm
Bitcoin Core disclosed CVE-2025-62860, where Tor connections were improperly trusted due to a -whitelist misconfiguration, and fixed versions 28.3, 29.2, and 30.0 were released in October 2025.
Bitcoin Core disclosed three vulnerabilities (one high, two medium) patched in October 2025, with details on mempool corruption blocking miners and DoS via witness tampering. Fixed versions are 30.0+ and 29.2+; no active exploitation or PoC mentioned.
The text reports that Bitcoin Core disclosed and fixed a Tor-related trust flaw (CVE-2025-62860) in which some nodes treated every inbound Tor connection as a trusted peer, patched in October 2025. Its main takeaway is the remediation call to update older Tor-running nodes, with no PoC, exploit tooling, or evidence of in-the-wild abuse cited.
The snippet only lists source URLs for a Bitcoin Core advisory and related articles, without providing any concrete details about the CVE, PoC, exploit, active exploitation, patch, or false‑positive status.
The text discloses a vulnerability (CVE-2025-62860) in Bitcoin Core involving an access control logic error where Tor inbound peers are incorrectly whitelisted when the -whitelist option is used, linking to the official vendor disclosure page.