Skip to content

Conversation

@fahedouch
Copy link

I am translating @stevespringett 's feedback on the CycloneDX VEX specification into the code.

Should ratings be normative inputs for prioritization in VEX consumers?

Yes, they should be. It is widely known that the NVD has historically overrated vulnerabilities (on purpose). So the ratings from the NVD and those from the manufactures are often different. CycloneDX can convey this information which can aid in prioritization.

fixes #719

"type": "array",
"title": "Ratings",
"description": "List of vulnerability ratings",
"description": "List of vulnerability ratings. Consumers SHOULD use ratings and SHOULD NOT ignore them; source ratings may differ and aid prioritization.",
Copy link
Author

@fahedouch fahedouch Nov 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I document how ratings should be interpreted and applied by consumers ?

@fahedouch fahedouch force-pushed the vex-ratings-actionable-cyclonedx-conumers branch from b2b999a to 93da22f Compare November 15, 2025 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE]: Make VEX Ratings Actionable in CycloneDX Consumers

1 participant