From: Greg Sanders <gsanders87@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Bitcoin Core security advisory for an easily discoverable vulnerability
Date: Fri, 20 Nov 2026 07:17:33 -0800 (PST) [thread overview]
Message-ID: <66d5e3d6-5a16-49ba-b7cc-442eb73252a5n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1361 bytes --]
Hi,
We just published 2 new releases to patch 1 medium severity security
vulnerability.
Fixed releases are available for all maintained major versions [^0]:
- 31.3: https://bitcoincore.org/en/2026/11/20/release-31.3/
- 30.5: https://bitcoincore.org/en/2026/11/20/release-30.5/
Our latest major version, 32.1, already includes the fix [^1].
The details for the vulnerability are available in the security advisory:
- https://bitcoincore.org/en/2026/11/20/disclose-orphan-inv-stall/
This advisory follows our accelerated process for easily discoverable
vulnerabilities.
See https://bitcoincore.org/en/security-advisories/ for more information on
our security disclosure
policy, or to consult historical security advisories.
Gregory Sanders
[^0]: Version 29 is also affected, but has reached end of life and will not
receive a fix. Users running 29.x should upgrade.
[^1]:
https://gnusha.org/pi/bitcoindev/c47ceea6-99de-41fe-a97c-928881963eccn@googlegroups.com/T/#u
--
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/66d5e3d6-5a16-49ba-b7cc-442eb73252a5n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1733 bytes --]
reply other threads:[~2026-11-20 16:07 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=66d5e3d6-5a16-49ba-b7cc-442eb73252a5n@googlegroups.com \
--to=gsanders87@gmail.com \
--cc=bitcoindev@googlegroups.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