Remote node crash via block-size check overflow
Published Mar 20, 2026 · Updated Mar 20, 2026
Integer overflow in Bitcoin Core 0.13.0 through 29.x allows remote attackers to crash 32-bit nodes with a pathological compact block. The pre-write block-size check overflows for blocks above 1 GB on 32-bit systems, allowing an oversized block to reach disk-writing logic and crash the process. Exploitation requires compact-block delivery and a non-default mempool above 3 GB that already holds about 1 GB of the block's transactions.
Summary
What happened
Integer overflow in Bitcoin Core 0.13.0 through 29.x allows remote attackers to crash 32-bit nodes with a pathological compact block. The pre-write block-size check overflows for blocks above 1 GB on 32-bit systems, allowing an oversized block to reach disk-writing logic and crash the process. Exploitation requires compact-block delivery and a non-default mempool above 3 GB that already holds about 1 GB of the block's transactions.
The record
- CVE
- CVE-2025-46597
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, CAPEC-92, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo