汇总 Bitcoin Core 相关全部产品的 CVE 与安全漏洞情报，包括 CVSS、EPSS、公开时间与漏洞情报数据。
已披露问题常与 路径处理缺陷、输入验证问题与跨站脚本 相关，可能在 生产负载与软件部署 场景中带来 内存损坏与文件覆盖 等暴露风险。
相关漏洞数据主要来源于公开漏洞披露与安全公告，可用于评估历史漏洞暴露面与修复优先级。
| CVE | 摘要 | 来源 | 最高 CVSS | EPSS % | 公开时间 | 更新时间 |
|---|---|---|---|---|---|---|
| CVE-2025-46597 | Bitcoin Core 0.13.0 through 29.x has an integer overflow. | [email protected] | 7.5 | 0.28% | 2026-03-20 | 2026-06-17 |
| CVE-2025-46598 | Bitcoin Core through 29.0 allows a denial of service via a crafted transaction. | [email protected] | 5.3 | 0.33% | 2026-03-20 | 2026-06-17 |
| CVE-2025-54605 | Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 2 of 2). | [email protected] | 7.5 | 0.35% | 2025-10-28 | 2026-06-17 |
| CVE-2025-54604 | Bitcoin Core through 29.0 allows Uncontrolled Resource Consumption (issue 1 of 2). | [email protected] | 7.5 | 0.35% | 2025-10-28 | 2026-06-17 |
| CVE-2024-55563 | 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 Lightning channel transactions. | [email protected] | 5.3 | 0.63% | 2024-12-08 | 2026-06-17 |
| CVE-2024-52922 | 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. | [email protected] | 6.5 | 0.32% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52921 | In Bitcoin Core before 25.0, a peer can affect the download state of other peers by sending a mutated block. | [email protected] | 5.3 | 0.43% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52920 | Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (infinite loop) via a malformed GETDATA message. | [email protected] | 7.5 | 0.61% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52919 | Bitcoin Core before 22.0 has a CAddrMan nIdCount integer overflow and resultant assertion failure (and daemon exit) via a flood of addr messages. | [email protected] | 6.5 | 0.27% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52917 | 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. | [email protected] | 6.5 | 0.27% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52916 | Bitcoin Core before 0.15.0 allows a denial of service (OOM kill of a daemon process) via a flood of minimum difficulty headers. | [email protected] | 7.5 | 0.51% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52915 | Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption) via a crafted INV message. | [email protected] | 7.5 | 0.62% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52914 | In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction. | [email protected] | 7.5 | 0.51% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52913 | 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. | [email protected] | 5.3 | 0.37% | 2024-11-17 | 2026-06-17 |
| CVE-2024-52912 | 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. | [email protected] | 7.5 | 0.52% | 2024-11-17 | 2026-06-17 |
| CVE-2019-25220 | 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 it. | [email protected] | 7.5 | 0.78% | 2024-11-17 | 2026-06-16 |
| CVE-2024-35202 | 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 PartiallyDownloadedBlock instance. | [email protected] | 7.5 | 0.90% | 2024-10-10 | 2026-06-17 |
| CVE-2023-50428 | 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 perspective of the Bitcoin Knots project, some others consider it "not a bug." | [email protected] | 5.3 | 0.78% | 2023-12-09 | 2026-06-17 |
| CVE-2023-37192 | 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. | [email protected] | 7.5 | 0.46% | 2023-07-06 | 2026-06-17 |
| CVE-2023-33297 | 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. | [email protected] | 7.5 | 1.40% | 2023-05-22 | 2026-06-17 |