Disk exhaustion via unbounded invalid-block logging
Published Oct 28, 2025 · Updated Oct 28, 2025
Uncontrolled log growth in Bitcoin Core 29.0 and earlier allows remote attackers to exhaust node disk space via repeated invalid blocks. The block-processing path writes an unconditional log entry when a block fails basic sanity checks or branches before the last checkpoint. No authentication or user interaction is required, but disk exhaustion requires sustained delivery because the fill rate is slow.
Summary
What happened
Uncontrolled log growth in Bitcoin Core 29.0 and earlier allows remote attackers to exhaust node disk space via repeated invalid blocks. The block-processing path writes an unconditional log entry when a block fails basic sanity checks or branches before the last checkpoint. No authentication or user interaction is required, but disk exhaustion requires sustained delivery because the fill rate is slow.
The record
- CVE
- CVE-2025-54605
- Published
- Oct 28, 2025
- Updated
- Oct 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 28, 2025CVE publishedPublication date reported by the CVE source.
- Oct 28, 2025Record 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