Bitcoin Core 32.0 entered release-candidate testing on September 14, 2026. A stable release was targeted for October 10, but we could not confirm the final release status, so check bitcoincore.org before upgrading. The release notes say version 32 makes no changes to Bitcoin’s consensus rules, which means no soft fork is involved.
The most notable security item is a memory-exhaustion bug that testers found in the node’s new HTTP server. Bitcoin Core 32 replaces the existing web server, and according to CoinDesk, an audit using Moonshot AI’s Kimi K3 model found that the replacement could keep accepting data from a client while it was still working through an earlier request. The data piled up in memory faster than the server could clear it. The same problem reached the REST interface, which can be used without login credentials.
Because the new server was never in a stable release, earlier stable versions are not affected, per CoinDesk and Forklog.
CoinDesk reports two test figures. Sixteen unauthenticated REST connections took one test node from about 46 MB of memory to about 3 GB in roughly a minute. In a separate 90-second test, memory reached 3.2 GB before the fix and about 3 MB after it. The fix is pull request 36123.
The rest of the 32.0 release
The memory bug gets the attention, but it isn’t the only change. A bug present since version 24.0 affected non-Windows systems that use the -walletnotify option with the %w placeholder. An authenticated RPC user with wallet-creation rights could craft a wallet name that broke shell escaping and ran an extra command. Version 32 treats the name as literal text. Forklog says it could not be exploited over normal P2P connections or without authorization.
Fee estimation changes too. The estimatesmartfee command adds a mempool_policy estimator beside block_policy. By default it uses both and returns the lower figure, so it can lower a recommended fee but never raise it. Block validation now prefetches prevout data in parallel, with 8 threads by default and a maximum of 16, and the speedup is largest when data must come from disk.
Four wallet commands now create version 2 PSBTs by default, and the older format stays available. After a full rebuild, the transaction index needs more than half the disk space. Existing indexes keep working but must be recreated to get the savings.
Who Benefits and How
Most people never run a node, so the benefit is indirect. The people who feel it first are node operators, who get a web server that testers fixed before it reached a stable release, plus a release that targets lower recommended fees and faster validation. Operators choose their own upgrade timing: read the final release notes and back up your wallet first, and don’t run a release candidate on a node that holds funds.
What the numbers don’t show
- The 46 MB to 3 GB and 3.2 GB to 3 MB figures come from tests reported by CoinDesk. They show the pattern, not what a real attacker would achieve against a production node.
- The wallet-name flaw needs an authenticated user and a specific option, so most nodes were not exposed.
- The fee estimator can only lower recommendations. Whether that saves you money depends on your wallet and on network conditions, and no savings figure has been published.
- We found no published sync-time measurement for the parallel validation change.
- October 10 was a target date. Release candidates can slip if testers find problems.
Quick answers
Were released versions vulnerable to the memory bug, and do I need to upgrade right away?
No to the first: the affected HTTP server had not shipped in a stable release. On timing, node operators decide for themselves, as described above.
Will fees fall for me?
Only if your wallet uses your node’s estimates. The change can only lower an estimate, and exact savings are unpublished.
Sources
- CoinDesk: Bitcoin Core 32 enters final testing with faster validation, fee changes and security fixes (Sep 16, 2026)
- Forklog: Bitcoin Core 32.0 enters final testing phase (Sep 2026)
- crypto.news: Bitcoin Core 32 enters final testing ahead of release (Sep 2026)
