admin: Amend SECURITY.md with recently assigned CVE numbers#5187
Merged
lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom May 5, 2026
Merged
admin: Amend SECURITY.md with recently assigned CVE numbers#5187lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom
lgritz merged 1 commit intoAcademySoftwareFoundation:mainfrom
Conversation
These are all items fixed and documented in the latest releases. I had hoped that the CVE reference numbers would be ready before I pushed those releases out. But let's just say that GitHub's "3 business days to assign a CVE" claim is aspirational. Signed-off-by: Larry Gritz <lg@larrygritz.com>
jessey-git
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These are all items fixed and documented in the latest releases. I had hoped that the CVE reference numbers would be ready before I pushed those releases out. But let's just say that GitHub's "3 business days to assign a CVE" claim is aspirational.