If you run a Bitcoin Core node, the version in use matters when assessing its security. A report published on November 19, 2026 summarizes disclosed vulnerabilities affecting versions before Bitcoin Core 30.0, organized by the version in which each was fixed.
The reported issues include a compact-block witness problem that can stall block processing; incoming Tor connections mistakenly being whitelisted; and TRUC relative eviction during a chain reorganization causing mempool inconsistency and potentially stopping block-template production. The summary also lists a remotely triggered crash on 32-bit systems, CPU denial of service during unconfirmed-transaction processing, disk exhaustion through log filling, a script-interpreter use-after-free, and an integer overflow in addr messages.
For node operators, the practical check is to compare the version they run with the fix version listed for each disclosure. The report says the individual disclosures include severity ratings, technical details, acknowledgments and timelines; the supplied summary does not provide those ratings or fix-version numbers.