Normalize severity casing in 2026 CVE advisories#1587
Merged
Conversation
The severity field in these four advisories used Title Case (High/Medium) while every other CVE under content/security/ uses UPPERCASE (HIGH/MEDIUM/LOW/CRITICAL). Bring them in line with the established convention so the YAML front matter and the clearsigned .txt.asc bodies are consistent across all advisories. The .txt.asc files have been re-signed after the change. Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
gansheer
approved these changes
May 6, 2026
Contributor
|
🚀 Preview is available at https://pr-1587--camel.netlify.app |
davsclaus
approved these changes
May 6, 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
3 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.
Summary
content/security/(CVE-2026-27172,CVE-2026-40453,CVE-2026-40473,CVE-2026-40858) used Title Case for theseverityfield (High/Medium), while every other CVE in the directory uses UPPERCASE (HIGH/MEDIUM/LOW/CRITICAL)..mdfront matter and the clearsigned.txt.ascbodies so the convention is consistent across all advisories..txt.ascfiles have been re-signed after the edit, so signature verification continues to pass.Test plan
grep -E '^severity:' content/security/CVE-*.md content/security/CVE-*.txt.ascshows only UPPERCASE values (ignoring the WIPCVE-2026-42527.mdplaceholder ofTODO).gpg --verify content/security/CVE-2026-27172.txt.asc(and the other three modified.txt.ascfiles) reports a good signature.