Bitcoin Core Discloses Three Flaws It Fixed in October 2025, One Rated High Severity
The high-severity flaw could stop a miner's node from producing blocks after a chain reorganization until it was restarted. In a network snapshot of 15 November 2026, 1,266 of 7,761 reachable Bitcoin Core peers, or 16.3 percent, announced a version in that flaw's affected range, by the Gazette's count; the snapshot does not show which of them build blocks.

Bitcoin Core published the details of three flaws on 10 November 2026, each fixed in releases of October 2025. It rates one of them High severity and two Medium.04 The project had announced the disclosure with its 32.1 release on 27 October, whose notes list "Medium and high severity vulnerabilities fixed in 30.0. There are 3 of these."05
The high-severity flaw, CVE-2025-62861, sat in the rules Bitcoin Core applies to version 3, or TRUC, transactions, each of which may have at most one unconfirmed parent and one unconfirmed child in a node's mempool, its pool of unconfirmed transactions. When a new transaction would give such a parent a second child, a rule called sibling eviction can remove the existing child if the new one pays enough, the advisory says. After a chain reorganization, a node puts the transactions of the dropped blocks back into its mempool; sibling eviction could still run at that moment and remove one of them while leaving behind transactions that spend it. A miner's node in that state can no longer assemble a valid block template, the draft of the block it would mine next, and "a node that performed such a reorg cannot produce blocks until it is restarted, which reloads the mempool in a consistent state." Versions 28.0 to 28.2 and 29.0 to 29.1 are affected. The fix shipped in 30.0 on 10 October 2025, in 29.2 on 14 October and in 28.3 on 17 October. Niklas Goegge reported the flaw to the project's security mailing list on 26 September 2025.0107 The Block called it "a high-severity flaw that could prevent affected mining nodes from creating valid block templates".14
CVE-2025-62859, rated Medium, concerns compact blocks, the short form in which peers announce a new block: its transactions are listed by short identifiers, and the receiving node rebuilds the block from transactions it already holds. Affected versions cleared a compact block's download state after rebuilding it but before one of its checks, for "witness malleation"; when that check failed, the node asked the same peer for the full block and waited up to ten minutes. A peer that announced a block to the node first could use this to stall its block processing. If the attacker controlled the node's three high-bandwidth peers, the ones a node lets send new blocks straight away, or the node ran with -blocksonly, a setting that turns off transaction relay, "this could be repeated indefinitely", the advisory says. It covers Bitcoin Core "before versions 29.2 and 30.0", the first releases with the fix, and names no first affected version. Eugene Siegel reported it on 28 April 2025.02 Neither 28.3 nor 28.4 lists the fix in its release notes.0809
CVE-2025-62860, also Medium, concerns the -whitelist option, which lifts some denial-of-service limits and privacy protections for trusted peers. An inbound Tor connection reaches a node from the address of its Tor daemon, which usually runs on the same machine or local network, so a whitelisted address range that covered the daemon also whitelisted every inbound Tor peer. Nodes without the non-default -whitelist option were never affected, the advisory says. Popular vendors, it says, bundled Bitcoin Core with a Tor daemon and set the option to the daemon's range: "This led to thousands of reachable mainnet nodes whitelisting all incoming Tor connections." The fix shipped in 30.0, 29.2 and 28.3. Martin Zumsande and Antoine Poinsot reported the flaw on 12 September 2025; on 17 September Poinsot reported it to the Bitcoin Knots maintainer, Luke Dashjr, "who acknowledges it on the same day".03
The timing follows the project's policy: "Medium and High severity vulnerabilities will be disclosed 2 weeks after the last affected release goes End of Life".04 The 29.x line, the last with affected releases, reached end of life on 27 October 2026; the details came 14 days later. Major versions at end of life "do not generally receive security fixes", the project's lifecycle page says.06
In the Karlsruhe Institute of Technology's network-monitor snapshot of 15 November 2026, 12:53 UTC, 7,761 of the 8,859 reachable peers the monitor was connected to advertised Bitcoin Core. Of those, 1,266, or 16.3 percent, announced a version in the range the high-severity advisory lists as affected: 981 on 28.0 to 28.2 and 285 on 29.0 or 29.1. That flaw affected only a node that builds block templates and went through a chain reorganization of the kind the advisory describes, and the snapshot does not show which nodes build them. A total of 3,092, or 39.8 percent, announced a version older than 29.2: 1,805 on 27.x or older, 1,002 on 28.x and 285 on 29.0 or 29.1. For CVE-2025-62860, 3,071, or 39.6 percent, announced a version without its fix; that flaw touched only nodes with -whitelist set, which the snapshot does not show. 4,537, or 58.5 percent, announced 29.2 or a later release, and 132 announced development builds. The figures are the Gazette's count of the version each peer's user agent states, over IPv4 and IPv6 only; a node can advertise any version.13
Bitcoin Knots, the next most common software in the snapshot, lists the same three fixes, under the same pull request numbers, in the notes of 29.2.knots20251010, published on 10 October 2025: #32646, the witness malleation check in compact blocks; #33395, which stops whitelist permissions applying to inbound Tor connections; and #33504, which stops the TRUC checks during a chain reorganization.10 As in Bitcoin Core's 29.2 notes and, for two of them, its 28.3 notes, they appear among other changes without being called security fixes. Knots' release notes name no CVE and do not say which earlier Knots releases carried each flaw. Its notes for 27.1.knots20240621, published on 23 June 2024, say of TRUC transactions: "By default, Bitcoin Knots v27.1 will accept, relay, and mine v3 transactions without these additional restrictions." The -mempooltruc option can be set to enforce them, the notes add.11 The notes of 29.4.3.knots20260508, of 28 October 2026, still name that setting.12 On the measure of the 39.8 percent of Core peers, a version older than 29.2, 80 of the 967 Knots peers in the snapshot, or 8 percent, announced a Knots release built on such a Bitcoin Core version: 46 on 28.1.knots20250305, 25 on 29.1.knots20250903, eight on 27.1.knots20240801 and one on 23.0.knots20220529. That count does not show whether any of those nodes was exposed to any of the three flaws.13
None of the three advisories says whether a flaw was used against a node.