#1162 Add Critical CVE Severity to support CVSS v3 scores 9.0-10.0#1178
Merged
Conversation
rushk014
approved these changes
Apr 16, 2026
Contributor
rushk014
left a comment
There was a problem hiding this comment.
Tested on 10.1.10.41:30010. LGTM pending backend asset view API update
…0-10.0 (Fixed bugs)
…0-10.0 (Fixed critical color in the PDF reports, Changed critical color for accessability)
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
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.
#1162
Added critical level related fields into every manager API's data model which includes scan result data.
Add styled critical level data display on the CVE severity badge, chart and statistic number's label.