Block propagation delay via repeated transaction validation
Published Mar 20, 2026 · Updated Mar 20, 2026
Resource exhaustion in Bitcoin Core 29.0 and earlier allows remote attackers to delay block propagation via crafted unconfirmed transactions. Transaction admission validates non-standard legacy Script and Tapscript inputs with worst-case signature hashing before rejecting them, while the peer remains connected. Any network peer can repeat the requests without authentication; each consumes seconds of CPU, delaying propagation rather than crashing the node.
Summary
What happened
Resource exhaustion in Bitcoin Core 29.0 and earlier allows remote attackers to delay block propagation via crafted unconfirmed transactions. Transaction admission validates non-standard legacy Script and Tapscript inputs with worst-case signature hashing before rejecting them, while the peer remains connected. Any network peer can repeat the requests without authentication; each consumes seconds of CPU, delaying propagation rather than crashing the node.
The record
- CVE
- CVE-2025-46598
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-405, T1499.002
- 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