Bitcoin Core
Source repositories
CVEs (62)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2025-46597 | Hig | 0.42 | 7.5 | 0.00 | Mar 20, 2026 | Bitcoin Core 0.13.0 through 29.x has an integer overflow. | ||
| CVE-2024-52922 | Med | 0.42 | 6.5 | 0.00 | Nov 18, 2024 | 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. | ||
| CVE-2024-52919 | Med | 0.42 | 6.5 | 0.00 | Nov 18, 2024 | Bitcoin Core before 22.0 has a CAddrMan nIdCount integer overflow and resultant assertion failure (and daemon exit) via a flood of addr messages. | ||
| CVE-2024-52918 | Med | 0.42 | 6.5 | 0.01 | Nov 18, 2024 | 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. | ||
| CVE-2024-52917 | Med | 0.42 | 6.5 | 0.00 | Nov 18, 2024 | 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. | ||
| CVE-2021-31876 | Med | 0.42 | 6.5 | 0.01 | May 13, 2021 | 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… | ||
| CVE-2016-10725 | Hig | 0.42 | 7.5 | 0.02 | Jul 5, 2018 | In Bitcoin Core before v0.13.0, a non-final alert is able to block the special "final alert" (which is supposed to override all other alerts) because operations occur in the wrong order. This behavior occurs in the remote network alert system (deprecated since Q1 2016). This… | ||
| CVE-2016-10724 | Hig | 0.42 | 7.5 | 0.02 | Jul 5, 2018 | Bitcoin Core before v0.13.0 allows denial of service (memory exhaustion) triggered by the remote network alert system (deprecated since Q1 2016) if an attacker can sign a message with a certain private key that had been known by unintended actors, because of an infinitely sized… | ||
| CVE-2017-18350 | Med | 0.38 | 5.9 | 0.02 | Mar 12, 2020 | bitcoind and Bitcoin-Qt prior to 0.15.1 have a stack-based buffer overflow if an attacker-controlled SOCKS proxy server is used. This results from an integer signedness error when the proxy server responds with an acknowledgement of an unexpected target domain name. | ||
| CVE-2018-20587 | Med | 0.36 | 5.5 | 0.00 | Feb 11, 2019 | Bitcoin Core 0.12.0 through 0.17.1 and Bitcoin Knots 0.12.0 through 0.17.x before 0.17.1.knots20181229 have Incorrect Access Control. Local users can exploit this to steal currency by binding the RPC IPv4 localhost port, and forwarding requests to the IPv6 localhost port. | ||
| CVE-2026-117350 | Med | 0.35 | 6.5 | 0.00 | Oct 30, 2026 | Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is vulnerable to an OOM issue. | ||
| CVE-2024-55563 | Med | 0.35 | 5.3 | 0.01 | Dec 9, 2024 | 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… | ||
| CVE-2018-20586 | Med | 0.35 | 5.3 | 0.01 | Mar 12, 2020 | bitcoind and Bitcoin-Qt prior to 0.17.1 allow injection of arbitrary data into the debug log via an RPC call. | ||
| CVE-2024-52921 | Med | 0.34 | 5.3 | 0.00 | Nov 18, 2024 | In Bitcoin Core before 25.0, a peer can affect the download state of other peers by sending a mutated block. | ||
| CVE-2024-52913 | Med | 0.34 | 5.3 | 0.00 | Nov 18, 2024 | 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. | ||
| CVE-2024-34149 | Med | 0.34 | 6.3 | 0.00 | Apr 30, 2024 | In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check (for example, because they agree with the objective but disagree with the… | ||
| CVE-2023-50428 | Med | 0.28 | 5.3 | 0.01 | Dec 9, 2023 | In Bitcoin Core through 26.0 and Bitcoin Knots before 25.1.knots20231115, datacarrier size limits can be bypassed by obfuscating data as code (e.g., with OP_FALSE OP_IF), as exploited in the wild by Inscriptions in 2022 and 2023. NOTE: although this is a vulnerability from the… | ||
| CVE-2026-117349 | Med | 0.27 | 5.3 | 0.00 | Oct 30, 2026 | Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is vulnerable to an OOM issue. | ||
| CVE-2025-46598 | Med | 0.27 | 5.3 | 0.00 | Mar 20, 2026 | Bitcoin Core through 29.0 allows a denial of service via a crafted transaction. | ||
| CVE-2024-35202 | Hig | 0.00 | 7.5 | 0.01 | Oct 10, 2024 | 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… |
- risk 0.42cvss 7.5epss 0.00
Bitcoin Core 0.13.0 through 29.x has an integer overflow.
- risk 0.42cvss 6.5epss 0.00
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.
- risk 0.42cvss 6.5epss 0.00
Bitcoin Core before 22.0 has a CAddrMan nIdCount integer overflow and resultant assertion failure (and daemon exit) via a flood of addr messages.
- risk 0.42cvss 6.5epss 0.01
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.
- risk 0.42cvss 6.5epss 0.00
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.
- risk 0.42cvss 6.5epss 0.01
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…
- risk 0.42cvss 7.5epss 0.02
In Bitcoin Core before v0.13.0, a non-final alert is able to block the special "final alert" (which is supposed to override all other alerts) because operations occur in the wrong order. This behavior occurs in the remote network alert system (deprecated since Q1 2016). This…
- risk 0.42cvss 7.5epss 0.02
Bitcoin Core before v0.13.0 allows denial of service (memory exhaustion) triggered by the remote network alert system (deprecated since Q1 2016) if an attacker can sign a message with a certain private key that had been known by unintended actors, because of an infinitely sized…
- risk 0.38cvss 5.9epss 0.02
bitcoind and Bitcoin-Qt prior to 0.15.1 have a stack-based buffer overflow if an attacker-controlled SOCKS proxy server is used. This results from an integer signedness error when the proxy server responds with an acknowledgement of an unexpected target domain name.
- risk 0.36cvss 5.5epss 0.00
Bitcoin Core 0.12.0 through 0.17.1 and Bitcoin Knots 0.12.0 through 0.17.x before 0.17.1.knots20181229 have Incorrect Access Control. Local users can exploit this to steal currency by binding the RPC IPv4 localhost port, and forwarding requests to the IPv6 localhost port.
- risk 0.35cvss 6.5epss 0.00
Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is vulnerable to an OOM issue.
- risk 0.35cvss 5.3epss 0.01
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…
- risk 0.35cvss 5.3epss 0.01
bitcoind and Bitcoin-Qt prior to 0.17.1 allow injection of arbitrary data into the debug log via an RPC call.
- risk 0.34cvss 5.3epss 0.00
In Bitcoin Core before 25.0, a peer can affect the download state of other peers by sending a mutated block.
- risk 0.34cvss 5.3epss 0.00
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.
- risk 0.34cvss 6.3epss 0.00
In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. NOTE: some parties oppose this new limit check (for example, because they agree with the objective but disagree with the…
- risk 0.28cvss 5.3epss 0.01
In Bitcoin Core through 26.0 and Bitcoin Knots before 25.1.knots20231115, datacarrier size limits can be bypassed by obfuscating data as code (e.g., with OP_FALSE OP_IF), as exploited in the wild by Inscriptions in 2022 and 2023. NOTE: although this is a vulnerability from the…
- risk 0.27cvss 5.3epss 0.00
Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is vulnerable to an OOM issue.
- risk 0.27cvss 5.3epss 0.00
Bitcoin Core through 29.0 allows a denial of service via a crafted transaction.
- risk 0.00cvss 7.5epss 0.01
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…
Page 2 of 4