From: "'Antoine Poinsot' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Three Bitcoin Core security advisories
Date: Tue, 10 Nov 2026 20:39:01 +0000 [thread overview]
Message-ID: <x8_ouI-b5d4xOuHCR353f-mt-bnpMdMK9joxUdYcVQdeiloXqBk2nZl1HNeyFPb-0a5Ef4z-v3EpT4NjjU85f6x5Cb2h-ZoVo7YrGcvEQ9E=@protonmail.com> (raw)
Hi,
Following the pre-announcement from two weeks ago, we are publishing today the details of three
security vulnerabilities affecting Bitcoin Core.
Two of those are medium severity. One is high severity. All of them are fixed in Bitcoin Core 29.2
and later 29.x releases, and in 30.0 and all later versions.
- CVE-2025-62861 is a mempool inconsistency bug in reorg handling, which can be exploited to prevent a
miner from obtaining valid block templates. https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62861/
- CVE-2025-62860 is an incorrect application of whitelist privileges on inbound Tor connections which
can be exploited to DoS a node, or make it leak internal state. https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62860/
- CVE-2025-62859 is a misplaced witness malleation check, which lets a malicious peer stall block
processing. https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62859/
For more information about Bitcoin Core's security disclosure policy, or to consult past security
advisories, see https://bitcoincore.org/en/security-advisories/
Antoine Poinsot
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/x8_ouI-b5d4xOuHCR353f-mt-bnpMdMK9joxUdYcVQdeiloXqBk2nZl1HNeyFPb-0a5Ef4z-v3EpT4NjjU85f6x5Cb2h-ZoVo7YrGcvEQ9E%3D%40protonmail.com.
reply other threads:[~2026-11-10 21:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='x8_ouI-b5d4xOuHCR353f-mt-bnpMdMK9joxUdYcVQdeiloXqBk2nZl1HNeyFPb-0a5Ef4z-v3EpT4NjjU85f6x5Cb2h-ZoVo7YrGcvEQ9E=@protonmail.com' \
--to=bitcoindev@googlegroups.com \
--cc=darosior@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox