I'm going to write up an official vulnerability disclosure policy for all my software projects. It will plainly state that I will publicly disclose vulnerabilities in the release notes, at the time a patched version is released. This is what I've been doing. The only change is that this will be clearer to my users.
I've been inspired by bitcoin core who kept a high severity vulnerability secret from all its users for a year.
I think that is inappropriate. I want my users to know that I will be transparent with my users.
And if people think it' a bad thing to disclose the impact of an issue that was fixed at the time the patch is available in a new release, they should be able to make an informed decision to not use my stuff.
And in fairness to bitcoin core, they do have a disclosure policy and a careful reading will show that they are following it.
"Medium and High severity vulnerabilities will be disclosed 2 weeks after..." but you have to read the rest of the sentence carefully because it doesn't do the normal thing of ending with "...when a patched version is released."
No, it ends with "...the last affected release goes End of Life (approximately a year after a major version containing the fix was first released)."
So my issue with their policy is almost entirely on me. I trusted that they were following the security best practices that have been established for decades. They are not. And had I taken the time to verify whether my expectations were being met, I wouldn't have felt so let down today. My bad. I can admit when I've made a mistake.
https://bitcoincore.org/en/2026/11/10/disclose-cve-2025-62861/https://bitcoincore.org/en/security-advisories/