According to ME News, on November 11 (UTC+8), a Bitcoin Core security advisory disclosed that the medium-severity vulnerability CVE-2025-62859 was made public on November 10, 2026. This vulnerability affects versions prior to 29.2 and 30.0, where a malicious node can exploit witness data manipulation within compact blocks to cause a victim’s block processing to stall under specific conditions. Affected nodes clear their download state after reconstructing a compact block but before verifying the witness data; if verification fails, the node switches to requesting a full block from the same peer and waits for a 10-minute timeout. If an attacker controls three high-bandwidth peer nodes of the victim, or if the victim is running in -blockonly mode, the attack can be repeated indefinitely. The fix is included in versions 29.2 and 30.0. (Source: ODAILY)
Bitcoin Core Discloses Medium-Risk Vulnerability Affecting Block Processing in Versions Prior to 29.2 and 30.0
KuCoinFlashShare
Bitcoin news: On November 10, 2026, Bitcoin Core disclosed a medium-risk vulnerability (CVE-2025-62859) affecting block processing in versions prior to 29.2 and 30.0. The flaw enables malicious nodes to exploit witness data in compact blocks, potentially triggering repeated full block requests and delays. A fix is available in versions 29.2 and 30.0. This vulnerability underscores the importance of timely upgrades to prevent service disruptions.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.
