{
 "updated": "2026-11-13T23:48:35Z",
 "source": "https://bitcoincore.org/en/security-advisories/",
 "note": "Titles, dates and severities as published by the Bitcoin Core project; summaries are each advisory's own excerpt.",
 "advisories": [
  {
   "date": "2018-09-20",
   "title": "Disclosure of CVE-2018-17144",
   "cve": [
    "CVE-2018-17144"
   ],
   "severity": null,
   "url": "https://bitcoincore.org/en/2018/09/20/notice/",
   "summary": "Bitcoin Core was vulnerable to a DoS and inflation attack. A fix was released on September 18th, 2018 in Bitcoin Core versions 0.16.3 and 0.17.0rc4."
  },
  {
   "date": "2019-11-08",
   "title": "Disclosure of CVE-2017-18350",
   "cve": [
    "CVE-2017-18350"
   ],
   "severity": null,
   "url": "https://bitcoincore.org/en/2019/11/08/CVE-2017-18350/",
   "summary": "Nodes were potentially vulnerable to a buffer overflow by malicious SOCKS servers. A fix was released on November 6th, 2017 in Bitcoin Core version 0.15.1."
  },
  {
   "date": "2024-07-03",
   "title": "CVE-2024-52918 - Crash using malicious BIP72 URI",
   "cve": [
    "CVE-2024-52918"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose-bip70-crash/",
   "summary": "The BIP70 implementation in Bitcoin-Qt could silently crash when opening a BIP72 URI. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0."
  },
  {
   "date": "2024-07-03",
   "title": "CVE-2024-52920 - DoS using huge GETDATA messages",
   "cve": [
    "CVE-2024-52920"
   ],
   "severity": "Low",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose-getdata-cpu/",
   "summary": "A malformed `GETDATA` message could trigger 100% CPU usage on the receiving node. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0."
  },
  {
   "date": "2024-07-03",
   "title": "CVE-2024-52916 - Memory DoS using low-difficulty headers",
   "cve": [
    "CVE-2024-52916"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose-header-spam/",
   "summary": "Nodes could be spammed with low-difficulty headers, which could be used to crash it. A fix was released on September 14th, 2017 in Bitcoin Core 0.15.0."
  },
  {
   "date": "2024-07-03",
   "title": "CVE-2024-52915 - Memory DoS using huge INV messages",
   "cve": [
    "CVE-2024-52915"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose-inv-buffer-blowup/",
   "summary": "Nodes would allocate up to 50 MB of memory per attacker sending a malicious `INV` message. A fix was released on June 3rd, 2020 in Bitcoin Core 0.20.0."
  },
  {
   "date": "2024-07-03",
   "title": "CVE-2024-52914 - Significant DoS due to orphan handling",
   "cve": [
    "CVE-2024-52914"
   ],
   "severity": "High",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose-orphan-dos/",
   "summary": "A node could be stalled for hours when receiving a specially crafted unconfirmed transaction. A fix was released on May 18th, 2019 in Bitcoin Core 0.18.0."
  },
  {
   "date": "2024-07-03",
   "title": "CVE-2024-52912 - Netsplit due to timestamp adjustment",
   "cve": [
    "CVE-2024-52912"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose-timestamp-overflow/",
   "summary": "A node could be split from the network when attacked by its first 200 peers. A fix was released on January 15th, 2021 in Bitcoin Core version 0.21.0."
  },
  {
   "date": "2024-07-03",
   "title": "Disclosure of CVE-2020-14198",
   "cve": [
    "CVE-2020-14198"
   ],
   "severity": "High",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose-unbounded-banlist/",
   "summary": "Nodes could be subject to CPU and memory DoS when attacked by lots of distinct IPs. A fix was released on August 1st, 2020 in Bitcoin Core 0.20.1."
  },
  {
   "date": "2024-07-03",
   "title": "CVE-2024-52913 - Censorship due to transaction re-request handling",
   "cve": [
    "CVE-2024-52913"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose_already_asked_for/",
   "summary": "Nodes could be prevented from seeing specific unconfirmed transactions by a malicious peer. A fix was released on January 14th, 2021 in Bitcoin Core 0.21.0."
  },
  {
   "date": "2024-07-03",
   "title": "Disclosure of CVE-2015-3641",
   "cve": [
    "CVE-2015-3641"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose_receive_buffer_oom/",
   "summary": "Attackers sending large incomplete messages would cause high memory usage. A fix was released on April 27th, 2015 in Bitcoin Core 0.10.1."
  },
  {
   "date": "2024-07-03",
   "title": "CVE-2015-20111 - Remote code execution due to bug in miniupnpc",
   "cve": [
    "CVE-2015-20111",
    "CVE-2015-6031"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/07/03/disclose_upnp_rce/",
   "summary": "A bug in the miniupnpc library could have led to a remote code execution in Bitcoin Core. A fix was released on October 15th, 2015 in Bitcoin Core 0.11.1."
  },
  {
   "date": "2024-07-31",
   "title": "CVE-2024-52919 - Remote crash due to addr message spam",
   "cve": [
    "CVE-2024-52919"
   ],
   "severity": "High",
   "url": "https://bitcoincore.org/en/2024/07/31/disclose-addrman-int-overflow/",
   "summary": "Nodes could be spammed with addr messsages, which could be used to crash them. A fix was released on September 14th, 2021 in Bitcoin Core v22.0."
  },
  {
   "date": "2024-07-31",
   "title": "CVE-2024-52917 - Infinite loop bug in the miniupnp dependency",
   "cve": [
    "CVE-2024-52917"
   ],
   "severity": "Low",
   "url": "https://bitcoincore.org/en/2024/07/31/disclose-upnp-oom/",
   "summary": "Nodes could be crashed by a malicious UPnP device on the local network. A fix was released on September 14th, 2021 in Bitcoin Core v22.0."
  },
  {
   "date": "2024-09-18",
   "title": "CVE-2019-25220 - Memory DoS due to headers spam",
   "cve": [
    "CVE-2019-25220"
   ],
   "severity": "High",
   "url": "https://bitcoincore.org/en/2024/09/18/disclose-headers-oom/",
   "summary": "An attacker could spam a Bitcoin Core node with low-difficulty headers chains, which could be used to remotely crash it."
  },
  {
   "date": "2024-10-08",
   "title": "Disclosure of CVE-2024-35202",
   "cve": [
    "CVE-2024-35202"
   ],
   "severity": "High",
   "url": "https://bitcoincore.org/en/2024/10/08/disclose-blocktxn-crash/",
   "summary": "An attacker could remotely crash a Bitcoin Core node by triggering an assertion in the blocktxn message handling logic."
  },
  {
   "date": "2024-10-08",
   "title": "Disclosure of DoS due to inv-to-send sets growing too large",
   "cve": [],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/10/08/disclose-large-inv-to-send/",
   "summary": "The inv-to-send sets could grow too large to a point where the time spent sorting the sets would affect the node's ability to communicate with its peers."
  },
  {
   "date": "2024-10-08",
   "title": "CVE-2024-52921 - Hindered block propagation due to mutated blocks",
   "cve": [
    "CVE-2024-52921"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/10/08/disclose-mutated-blocks-hindering-propagation/",
   "summary": "A peer could hinder block propagation by sending mutated blocks."
  },
  {
   "date": "2024-11-05",
   "title": "CVE-2024-52922 - Hindered block propagation due to stalling peers",
   "cve": [
    "CVE-2024-52922"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2024/11/05/cb-stall-hindering-propagation/",
   "summary": "A peer could hinder block propagation by announcing blocks first and then simply withholding the block."
  },
  {
   "date": "2025-04-28",
   "title": "CVE-2024-52919 - Remote crash due to addr message spam (part 2)",
   "cve": [
    "CVE-2024-52919"
   ],
   "severity": "Low",
   "url": "https://bitcoincore.org/en/2025/04/28/disclose-cve-2024-52919/",
   "summary": "An attacker could crash a node by spamming it with `addr` messages for a very long time. A fix was released on April 14th 2025 in Bitcoin Core v29.0."
  },
  {
   "date": "2025-10-24",
   "title": "CVE-2025-46597 - Highly unlikely remote crash on 32-bit systems",
   "cve": [
    "CVE-2025-46597"
   ],
   "severity": "Low",
   "url": "https://bitcoincore.org/en/2025/10/24/disclose-cve-2025-46597/",
   "summary": "An attacker could produce a block that crashes nodes running on 32-bit systems in a rare edge case. A fix was released on October 10th 2025 in Bitcoin Core v30.0."
  },
  {
   "date": "2025-10-24",
   "title": "CVE-2025-46598 - CPU DoS from unconfirmed transaction processing",
   "cve": [
    "CVE-2025-46598"
   ],
   "severity": "Low",
   "url": "https://bitcoincore.org/en/2025/10/24/disclose-cve-2025-46598/",
   "summary": "Specially crafted invalid unconfirmed transactions could cause unnecessary resource usage. A fix was released on October 10th 2025 in Bitcoin Core v30.0."
  },
  {
   "date": "2025-10-24",
   "title": "CVE-2025-54604 - Disk filling from spoofed self connections",
   "cve": [
    "CVE-2025-54604"
   ],
   "severity": "Low",
   "url": "https://bitcoincore.org/en/2025/10/24/disclose-cve-2025-54604/",
   "summary": "An attacker could cause a victim node to fill up its disk space by repeatedly faking self-connections over a long time. A fix was released on October 10th 2025 in Bitcoin Core v30.0."
  },
  {
   "date": "2025-10-24",
   "title": "CVE-2025-54605 - Disk filling from invalid blocks",
   "cve": [
    "CVE-2025-54605"
   ],
   "severity": "Low",
   "url": "https://bitcoincore.org/en/2025/10/24/disclose-cve-2025-54605/",
   "summary": "An attacker could cause a victim node to fill up its disk space by repeatedly sending invalid blocks. A fix was released on October 10th 2025 in Bitcoin Core v30.0."
  },
  {
   "date": "2026-05-05",
   "title": "CVE-2024-52911 - Script Interpreter Remote Crash",
   "cve": [
    "CVE-2024-52911"
   ],
   "severity": "High",
   "url": "https://bitcoincore.org/en/2026/05/05/disclose-cve-2024-52911/",
   "summary": "A specially-crafted block can be used to remotely crash a Bitcoin Core node by exploiting a use-after-free in its script interpreter."
  },
  {
   "date": "2026-10-28",
   "title": "CVE-2026-117349 - Slow unbounded memory growth on paused pre-BIP31 peers",
   "cve": [
    "CVE-2026-117349"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2026/10/28/disclose-fpausesend-oom/",
   "summary": "Bitcoin Core queues announcements for all peers, including paused ones. Pre-BIP31 peers could stay paused forever and let the queue grow unboundedly."
  },
  {
   "date": "2026-10-28",
   "title": "CVE-2026-117350 - Unbounded memory growth through TCP urgent data on non-Linux systems",
   "cve": [
    "CVE-2026-117350"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2026/10/28/disclose-tcp-oom/",
   "summary": "On platforms other than Linux, a malicious peer could cause a node to run out of memory by sending TCP urgent (out-of-band) data."
  },
  {
   "date": "2026-10-28",
   "title": "CVE-2026-117346 - Undo file overflow under extreme conditions",
   "cve": [
    "CVE-2026-117346"
   ],
   "severity": "Low",
   "url": "https://bitcoincore.org/en/2026/10/28/disclose-undo-overflow/",
   "summary": "After filling thousands of blocks in preparation, a miner able to trigger a precisely timed short reorg following a specific sequence of blocks could crash some nodes by corrupting their undo data. A fix for 64-bit systems was released in Bitcoin Core versions 29.5, 30.4, 31.2 and 32.1; 32-bit systems and nodes storing blocks on FAT32 remain affected."
  },
  {
   "date": "2026-11-10",
   "title": "CVE-2025-62859 - Block processing stall via witness malleation",
   "cve": [
    "CVE-2025-62859"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62859/",
   "summary": "Block processing may be stalled by a peer announcing a compact block with a malleated witness"
  },
  {
   "date": "2026-11-10",
   "title": "CVE-2025-62860 - Inbound Tor connections wrongly receive -whitelist permissions",
   "cve": [
    "CVE-2025-62860"
   ],
   "severity": "Medium",
   "url": "https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/",
   "summary": "Various DoS and privacy protections were lifted for incoming Tor connections on affected nodes."
  },
  {
   "date": "2026-11-10",
   "title": "CVE-2025-62861 - Block template creation halted by TRUC sibling eviction during reorg",
   "cve": [
    "CVE-2025-62861"
   ],
   "severity": "High",
   "url": "https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62861/",
   "summary": "A chain reorganization could trigger erroneous \"sibling eviction\" of TRUC (v3) transactions, corrupting the mempool so an affected node can no longer create block templates until it is restarted. A fix was released on October 10th 2025 in Bitcoin Core v30.0."
  }
 ]
}