A supplied report says Bitcoin Core addressed three security vulnerabilities in October 2025 through releases 30.0 on October 10 and 29.2 on October 14. It identifies CVE-2025-62861 as the most serious issue, affecting versions 28.0 through 28.2, along with 29.0 and 29.1. A surfaced Bitcoin Core advisory snippet adds that the Tor-related bug caused inbound connections to incorrectly receive trusted permissions.

Which Bitcoin Core Versions Were Reportedly Patched

The supplied report says the three vulnerabilities were addressed in Bitcoin Core 30.0 on 2025-10-10 and 29.2 on 2025-10-14. For the main issue, CVE-2025-62861, it identifies versions 28.0 through 28.2, plus 29.0 and 29.1, as affected. This provides the clearest supported exposure map: a node or mining setup still running those releases falls within the reported risk window.

Two secondary snippets broaden the reported patch path. BeInCrypto and Security Online also identify Bitcoin Core 28.3 as a patched release, suggesting the 28.x branch may have received its own security update in addition to 29.2 and 30.0. Because the underlying release notes and advisories were not directly reviewed here, the 28.3 detail should be treated as a reported extension of the fix path rather than a fully confirmed branch matrix.

The version picture is the main operational takeaway, as the story is less about a failure of Bitcoin itself than about whether specific Bitcoin Core builds remained exposed after the October releases.

What the Three Bugs Reportedly Affected

The supplied report says CVE-2025-62861 was the most serious because it could disrupt miners' ability to produce new blocks under certain conditions. This is most relevant to mining operations and setups that rely on valid block-template generation, rather than to casual observers following the network from a distance.

The same report describes CVE-2025-62859 as a block-processing slowdown issue. According to the report, a malicious participant could alter transaction witness data and cause an affected node to wait up to 10 minutes before processing a block. This indicates delayed processing, rather than an established consensus failure or a proven network-wide outage.

The Tor-related issue is narrower than the original alert wording suggests. A search snippet from Bitcoin Core's security-advisories page describes CVE-2025-62860 as inbound Tor connections incorrectly receiving -whitelist permissions, removing various denial-of-service and privacy protections for those connections. In practical terms, the bug is most relevant to operators using Tor-based connectivity and trust settings, rather than necessarily to every Bitcoin Core user.

What October Patching Means for Upgrade Timing

The reported October dates matter because they define the patch-release window in the current account: version 30.0 on October 10 and 29.2 on October 14. For readers asking whether the bugs were patched, the direct answer is that they were reported as fixed in those releases, while separate secondary coverage also points to 28.3.

A later date in coverage does not necessarily change that timeline. A BeInCrypto snippet says an advisory for CVE-2025-62861 was published on November 10, which may reflect the later public disclosure of technical details rather than a different patch date. Without the full advisory page, the most cautious reading is that October refers to the release of patches, while November may refer to a later vulnerability write-up.

This leaves a narrow but useful conclusion: operators should check whether they are still running the specifically named affected versions, while Tor users should pay particular attention to the permission issue surfaced in the Bitcoin Core snippet. The available material does not establish that every branch received identical fixes or that maintainers issued a single formal emergency directive for all users.