From: Niklas Goegge <n.goeggi@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Public disclosure of one high severity Bitcoin Core advisory (CVE-2024-52911)
Date: Tue, 5 May 2026 06:17:45 -0700 (PDT) [thread overview]
Message-ID: <dd3a05f3-19a5-42ab-9680-2bd897df8d4en@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 943 bytes --]
Hi everyone,
In accordance with our security disclosure policy, we are sharing one
advisory for a
*high-severity* security vulnerability fixed in Bitcoin Core version 29.0
and above.
The detailed advisory can be found here:
https://bitcoincore.org/en/2026/05/05/disclose-cve-2024-52911/.
Thanks to Cory Fields for reporting this issue and to everyone involved in
fixing it.
Our disclosure policy as well as previously disclosed vulnerabilities are
available on the Bitcoin Core website at
https://bitcoincore.org/en/security-advisories/.
Niklas Goegge
--
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/dd3a05f3-19a5-42ab-9680-2bd897df8d4en%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1412 bytes --]
next reply other threads:[~2026-05-05 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 13:17 Niklas Goegge [this message]
2026-05-06 0:25 ` [bitcoindev] Re: Public disclosure of one high severity Bitcoin Core advisory (CVE-2024-52911) Antoine Riard
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=dd3a05f3-19a5-42ab-9680-2bd897df8d4en@googlegroups.com \
--to=n.goeggi@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