B
CVE Numbering Authority
redhat Red Hat, Inc.
- Country
- USA
- Organization type
- Vendor, Open Source
- Program role
- Root,CNA-LR,CNA
- Root
- mitre
- Scope
- Root Scope: The Red Hat Root’s scope includes the open source community. Any open source organizations that prefer Red Hat as their Root; organizations are free to choose another Root if it suits them better. CNA-LR Scope: Vulnerabilities in software developed by a CNA within the Red Hat Root hierarchy. CNA Scope: Vulnerabilities in open source projects affecting Red Hat software that are not covered by a more specific CNA. CVEs can be assigned to vulnerabilities affecting end-of-life or unsupported Red Hat software.
82.25/100 over 1,212 records
in the last 180 days
· 42.02/100 over 12,112 all-time
The rules, last 180 days
Share of the records earning each credit, and the points it is worth.
Describe: can a reader tell what the vulnerability is?
24.92 / 25Description
An English description that is not a placeholder: full credit from 200 characters, 0.7 from 80, 0.4 from 40, none below.
99% · 9.94/10
Title
A title.
100% · 5.0/5
Cwe
A weakness as a CWE identifier in problemTypes; a free-text problem type without one earns a quarter.
100% · 9.98/10
Scope: can a reader tell whether they are affected?
23.15 / 25Affected
An affected entry naming both a vendor and a product; one side missing or 'n/a' earns half.
99% · 9.88/10
Versions
An affected entry stating versions, as a version or a bound; a defaultStatus alone earns half.
80% · 6.39/8
Cpe
A CPE on an affected entry, or a cpeApplicability block.
98% · 6.88/7
Assess: can a reader tell how bad it is?
15.0 / 25Severity
A severity statement in the CNA container: a CVSS v3 or v4 vector, an SSVC decision, or a vendor rating as an 'other' metric. A CVSS v2 vector alone earns half.
100% · 15.0/15
Modern severity
A CVSS v4 vector or an SSVC decision.
0% · 0.0/5
Impacts
An impacts entry (a CAPEC identifier or an impact description).
0% · 0.0/5
Act: can a reader tell what to do about it?
19.19 / 25References
At least one reference.
100% · 7.0/7
Reference tags
At least one reference carrying tags.
100% · 4.99/5
Remediation
A reference tagged 'patch'; one tagged 'vendor-advisory', 'mitigation' or 'release-notes' earns 0.6.
35% · 2.8/8
Solutions
A solution or a workaround.
88% · 4.4/5
Context, not score
- Severity supplied by an ADP
- 0% (3 records)
- Weakness supplied by an ADP
- 0% (2 records)
- No severity statement
- 0%
- Descriptions under 100 characters
- 0%
- Known exploited
- 1
- Reservation to publication
- median 3.9 days · p90 48.0 days
- Rejected records
- 19
Score per publication year
| 2026 | 82.38 | 1,417 |
| 2025 | 83.02 | 300 |
| 2024 | 81.48 | 306 |
| 2023 | 62.85 | 446 |
| 2022 | 44.53 | 627 |
| 2021 | 46.13 | 452 |
| 2020 | 49.61 | 567 |
| 2019 | 50.52 | 630 |
| 2018 | 59.01 | 562 |
| 2017 | 26.86 | 477 |
| 2016 | 25.24 | 537 |
| 2015 | 25.5 | 400 |
| 2014 | 24.77 | 950 |
| 2013 | 25.76 | 970 |
| 2012 | 23.98 | 1,156 |
| 2011 | 25.42 | 515 |
| 2010 | 25.67 | 464 |
| 2009 | 26.09 | 311 |
| 2008 | 26.35 | 272 |
| 2007 | 25.97 | 244 |
| 2006 | 26.25 | 270 |
| 2005 | 25.05 | 239 |
Badge