A late report changed the release plan
Bitcoin Core maintainers added a patch for a newly reported out-of-memory bug affecting non-Linux nodes to a set of accelerated maintenance releases, according to the Bitcoin Optech Newsletter #429 Recap Podcast, published Nov. 3, 2026. The podcast says the team had been preparing accelerated fixes for two other bugs when this issue arrived.
The report describes the affected systems as non-Linux nodes, but does not provide the bug’s technical details or identify the specific release versions in this excerpt.
Different urgency among the bundled bugs
The Bitcoin Optech podcast says this was the first use of the approach for issues it characterized as easily discoverable. It also distinguishes the three issues included in the accelerated releases: the newly reported bug, another out-of-memory issue, and an undo-file overflow.
We picked these issues because the other OOM issue is reasonably severe, but it’s not as bad as the other one, because it’s slower to exploit. And the undo file overflow is merely theoretical.
That assessment comes from the podcast’s account of the maintainers’ reasoning. It characterizes the other out-of-memory issue as slower to exploit and the undo-file overflow as theoretical; it does not give further details about their relative severity.
Binaries were prepared across maintained versions
The Bitcoin Optech podcast says binaries for all maintained versions were released within 48 hours of the pull requests becoming public. That is the interval reported from the public opening of the PRs, not a time measured from the initial discovery of the bug.
The excerpt does not name the release dates or specify which versions users should install. Its account is a dated report of the accelerated release process, not confirmation that the releases are newly available now.
The operating-system explanation is qualified
The Bitcoin Optech podcast offers a tentative explanation for why the issue affected systems differently: it says Patrick Strateman changed how Linux handled the relevant method in 2018, while Windows, FreeBSD and other systems were not changed, possibly because of how they would handle it. The speaker explicitly qualifies this account as being based on their understanding, so the excerpt does not establish the full technical cause.