From: "'Antoine Poinsot' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] 3 Bitcoin Core security advisories for easily discoverable vulnerabilities
Date: Wed, 28 Oct 2026 18:36:19 +0000 [thread overview]
Message-ID: <vf_yceciSS4HUGwYYk6tuj8ndp-JKV5q2OBS9HKVaSRkO1ggCKxLEy3mS6rkL7tG3XLpRFS1pme4Niz83LUJeQNJNH8lHuyo_8ynAj_qRY4=@protonmail.com> (raw)
Hi,
We just published 4 new releases to patch 2 medium severity and 1 low severity security vulnerabilities.
Fixed releases are available for all past major versions [^0]:
- 32.1: https://bitcoincore.org/en/2026/10/27/release-32.1/
- 31.2: https://bitcoincore.org/en/2026/10/28/release-31.2/
- 30.4: https://bitcoincore.org/en/2026/10/28/release-30.4/
- 29.5: https://bitcoincore.org/en/2026/10/28/release-29.5/
The details for each vulnerability are available in the corresponding security advisory:
- https://bitcoincore.org/en/2026/10/28/disclose-tcp-oom/
- https://bitcoincore.org/en/2026/10/28/disclose-fpausesend-oom/
- https://bitcoincore.org/en/2026/10/28/disclose-undo-overflow/
These advisories are following our accelerated process for easily discoverable vulnerabilities. The
release of fixed versions happens to coincide with the release of our latest major version, 32.1 [^1].
The 3 vulnerabilities pre-announced along with our latest major release, 32.1, are unrelated to the
easily discoverable vulnerabilities above. Their disclosure goes through our regular process, and we
will share the details for those in 2 weeks.
See https://bitcoincore.org/en/security-advisories/ for more information on our security policy
disclosure, or to consult historical security advisories.
Antoine Poinsot
[^0]: Including 29, which was then immediately made EOL by the release of major version 32.
[^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/vf_yceciSS4HUGwYYk6tuj8ndp-JKV5q2OBS9HKVaSRkO1ggCKxLEy3mS6rkL7tG3XLpRFS1pme4Niz83LUJeQNJNH8lHuyo_8ynAj_qRY4%3D%40protonmail.com.
reply other threads:[~2026-10-28 18:57 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='vf_yceciSS4HUGwYYk6tuj8ndp-JKV5q2OBS9HKVaSRkO1ggCKxLEy3mS6rkL7tG3XLpRFS1pme4Niz83LUJeQNJNH8lHuyo_8ynAj_qRY4=@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