How the crash could happen

Bitcoin Core says the issue involved TCP urgent data on the socket-monitoring backend used outside Linux. A malicious peer could bypass the normal backpressure mechanism and keep adding data to a queue until the node ran out of memory.

The disclosure describes the issue as medium severity and easily discoverable. The fix shipped in Bitcoin Core 32.1 and supported backport releases.

Who should act

If you run a reachable Bitcoin Core node on Windows, macOS or BSD, update to a fixed release from the official Bitcoin Core download site and verify signatures. Users who only hold bitcoin in a wallet and do not run a full node are not directly operating the affected service.

PRIMARY SOURCES

Evidence you can open

01
Bitcoin Core vulnerability disclosureTechnical details, affected systems and timeline.
OPEN ↗
02
Bitcoin Core 32.1 releaseOfficial release notice and download path.
OPEN ↗