Revise CVE ID handling guidelines in contributor guide #298
+2
−6
Conversation
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
Clarified guidelines for reserving and managing CVE IDs based on: https://www.cve.org/Resources/Roles/Cnas/CNA_Rules_v4.0.pdf Section 4.2.2
ljharb
approved these changes
Sep 30, 2025
|
@UlisesGascon would love one more pair of eyes on this one, if you approve we can merge. Note I fully expect future changes and adjustments. |
UlisesGascon
approved these changes
Oct 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I merged an initial commit with the exact same info as the google doc and created a PR for this one so we could have a discussion about changes. In this pr...
Clarified guidelines for reserving and managing CVE IDs based on:
https://www.cve.org/Resources/Roles/Cnas/CNA_Rules_v4.0.pdf
Section 4.2.2