HighCVSS 7.5
Bitcoin Core 0.13.0 through 29.x has an integer overflow.
Vendor
bitcoin vulnerabilities
56 published CVES affecting bitcoin, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 56
- Critical
- 2
- High
- 25
- Medium
- 29
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Products
Latest bitcoin CVEs
Newest publication first · page 1 of 3
-
-
CVE-2025-46598 Bitcoin Core through 29.0 allows a denial of service via a crafted transaction.
PublishedMediumCVSS 5.3Bitcoin Core through 29.0 allows a denial of service via a crafted transaction.
-
CVE-2025-54605 Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 2 of 2).
PublishedHighCVSS 7.5Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 2 of 2).
-
CVE-2025-54604 Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 1 of 2).
PublishedHighCVSS 7.5Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 1 of 2).
-
MediumCVSS 5.3
Bitcoin Core through 27.2 allows transaction-relay jamming via an off-chain protocol attack, a related issue to CVE-2024-52913. For example, the outcome of an HTLC (Hashed Timelock Contract) can be changed because a flood of transaction traffic prevents propagation of certain Lig...
-
HighCVSS 7.5
Bitcoin Core before 24.0.1 allows remote attackers to cause a denial of service (daemon crash) via a flood of low-difficulty header chains (aka a "Chain Width Expansion" attack) because a node does not first verify that a presented chain has enough work before committing to store...
-
HighCVSS 7.5
Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (infinite loop) via a malformed GETDATA message.
-
HighCVSS 7.5
In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction.
-
MediumCVSS 6.5
Bitcoin-Qt in Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption and application crash) via a BIP21 r parameter for a URL that has a large file.
-
MediumCVSS 5.3
In Bitcoin Core before 25.0, a peer can affect the download state of other peers by sending a mutated block.
-
MediumCVSS 5.3
In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled.
-
MediumCVSS 6.5
Bitcoin Core before 22.0 has a CAddrMan nIdCount integer overflow and resultant assertion failure (and daemon exit) via a flood of addr messages.
-
HighCVSS 7.5
Bitcoin Core before 0.15.0 allows a denial of service (OOM kill of a daemon process) via a flood of minimum difficulty headers.
-
MediumCVSS 6.5
Bitcoin Core before 22.0 has a miniupnp infinite loop in which it allocates memory on the basis of random data received over the network, e.g., large M-SEARCH replies from a fake UPnP device.
-
MediumCVSS 6.5
In Bitcoin Core before 25.1, an attacker can cause a node to not download the latest block, because there can be minutes of delay when an announcing peer stalls instead of complying with the peer-to-peer protocol specification.
-
HighCVSS 7.5
Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption) via a crafted INV message.
-
HighCVSS 7.5
Bitcoin Core before 0.21.0 allows a network split that is resultant from an integer overflow (calculating the time offset for newly connecting peers) and an abs64 logic bug.
-
CriticalCVSS 9.8
miniupnp before 4c90b87, as used in Bitcoin Core before 0.12 and other products, lacks checks for snprintf return values, leading to a buffer overflow and significant data leak, a different vulnerability than CVE-2019-12107. In Bitcoin Core before 0.12, remote code execution was...
-
HighCVSS 7.5
Bitcoin Core before 25.0 allows remote attackers to cause a denial of service (blocktxn message-handling assertion and node exit) by including transactions in a blocktxn message that are not committed to in a block's merkle root. FillBlock can be called twice for one PartiallyDow...
-
HighCVSS 7.5
Memory management and protection issues in Bitcoin Core v22 allows attackers to modify the stored sending address within the app's memory, potentially allowing them to redirect Bitcoin transactions to wallets of their own choosing.
-
HighCVSS 7.5
Bitcoin Core before 24.1, when debug mode is not used, allows attackers to cause a denial of service (e.g., CPU consumption) because draining the inventory-to-send queue is inefficient, as exploited in the wild in May 2023.
-
MediumCVSS 6.5
Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a loss of funds, or a denial of service attack against downstream projects such as Lightning network nodes. An unconfirmed chi...
-
CriticalCVSS 9.8
Bitcoin Core before 0.19.0 might allow remote attackers to execute arbitrary code when another application unsafely passes the -platformpluginpath argument to the bitcoin-qt program, as demonstrated by an x-scheme-handler/bitcoin handler for a .desktop file or a web browser. NOTE...
-
HighCVSS 7.5
Bitcoin Core 0.20.0 allows remote denial of service.
-
HighCVSS 7.5 EPSS 4.8%
Bitcoin Core 0.16.x before 0.16.2 and Bitcoin Knots 0.16.x before 0.16.2 allow remote denial of service via a flood of multiple transaction inv messages with random hashes, aka INVDoS. NOTE: this can also affect other cryptocurrencies, e.g., if they were forked from Bitcoin Core...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.