–
CVE Numbering Authority
anthropic
65.0/100 over 1 record
in the last 180 days (under the threshold of 10, not ranked)
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?
20.0 / 25Description
An English description that is not a placeholder: full credit from 200 characters, 0.7 from 80, 0.4 from 40, none below.
100% · 10.0/10
Title
A title.
0% · 0.0/5
Cwe
A weakness as a CWE identifier in problemTypes; a free-text problem type without one earns a quarter.
100% · 10.0/10
Scope: can a reader tell whether they are affected?
18.0 / 25Affected
An affected entry naming both a vendor and a product; one side missing or 'n/a' earns half.
100% · 10.0/10
Versions
An affected entry stating versions, as a version or a bound; a defaultStatus alone earns half.
100% · 8.0/8
Cpe
A CPE on an affected entry, or a cpeApplicability block.
0% · 0.0/7
Assess: can a reader tell how bad it is?
20.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.
100% · 5.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?
7.0 / 25References
At least one reference.
100% · 7.0/7
Reference tags
At least one reference carrying tags.
0% · 0.0/5
Remediation
A reference tagged 'patch'; one tagged 'vendor-advisory', 'mitigation' or 'release-notes' earns 0.6.
0% · 0.0/8
Solutions
A solution or a workaround.
0% · 0.0/5
Context, not score
- Severity supplied by an ADP
- 0% (0 records)
- Weakness supplied by an ADP
- 0% (0 records)
- No severity statement
- 0%
- Descriptions under 100 characters
- 0%
- Known exploited
- 0
- Reservation to publication
- median 0.6 days · p90 0.6 days
- Rejected records
- 0
Badge