CVE-2025-54604
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 1 of 2).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBitcoin Core through version 29.0 contains an uncontrolled resource consumption vulnerability that could allow an attacker to exhaust system resources (likely memory, CPU, or network bandwidth), potentially leading to denial of service. The specific attack vector and affected component are not detailed in the available information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 30.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Bitcoin Core versionRun 'bitcoin-cli getnetworkinfo' or 'bitcoind -version' to retrieve the installed version numberAffected if Version is below 30.0 (e.g., 29.0, 28.x, 27.x, etc.)
-
Verify Bitcoin Core daemon statusRun 'bitcoin-cli getblockchaininfo' or check process status (ps aux | grep bitcoind) to confirm bitcoind is runningAffected if Bitcoin Core daemon is actively running and version is below 30.0
-
Check RPC interface exposureReview bitcoin.conf for 'rpcbind' or 'rpcallowip' settings, or run 'bitcoin-cli getnetworkinfo' to check RPC endpointsAffected if RPC interface is exposed to untrusted networks (0.0.0.0 or public IP ranges) and version is below 30.0
-
Check P2P network listening statusRun 'bitcoin-cli getnetworkinfo' and look for 'localservices' or check if 'listen' is enabled in bitcoin.confAffected if Node is accepting incoming P2P connections (listen=true) and version is below 30.0
Environment is affected if Bitcoin Core version is below 30.0 and the daemon is running with network exposure (P2P or RPC interfaces).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped30.0
Apply the latest Bitcoin Core security update/patch when released by the Bitcoin Core project to address the uncontrolled resource consumption issue.
Bitcoin Core 30.0
- 1. Backup your Bitcoin Core data directory and any wallets before upgrading
- 2. Stop the running Bitcoin Core service or close the application
- 3. Download Bitcoin Core version 30.0 from the official source at bitcoincore.org
- 4. Verify the GPG signature of the downloaded binary using the Bitcoin Core release keys to ensure authenticity
- 5. Replace the existing Bitcoin Core installation with version 30.0
- 6. Restart the Bitcoin Core service or application
- 7. Monitor logs to confirm the node is running correctly on version 30.0
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54604 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54604 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data