Bitcoin Core disclosed 3 vulnerabilities all at once
2 medium severity, 1 low severity—and not a single CVE number assigned
The most striking one: a malicious node can send a special kind of network data
and exhaust the memory of nodes on Windows and macOS, causing them to crash
Linux nodes, however, dodged this one

Another one is sneakier
An attacker pretends to use the old protocol to avoid being disconnected by a timeout
Each inbound connection can consume about 2 MB of extra memory per hour
Outbound connections are worse, at about 5 MB
The third requires miners to mine thousands of specially crafted blocks to pull off
But 32-bit systems and FAT32 drives remain exposed even after the fix

The fixes are included in 29.5, 30.4, 31.2, and 32.1
32.1 also raised the node connection limit
The official wording is very clear: in two weeks,
they’ll disclose another 3 medium-to-high severity vulnerabilities fixed in 30.0

My take:
No one lost coins this time, and the chain didn’t stop
The real risk is for people running old versions and self-hosting nodes on Windows
Exchanges and mining pools will upgrade immediately
Many full nodes run by retail users haven’t been touched in six months
Open-source code is checking itself for vulnerabilities
Nodes that don’t upgrade are the weakest link on this machine
$BTC is now around 80.2K, and the market has barely reacted
Those three medium-to-high severity vulnerabilities coming in two weeks are the second shoe to watch

$BTC $BNB
#比特币Core发现三个漏洞 #BitcoinCore releases version 32.1, raises node connection limit #BTC