CVE
What each publisher says about a vulnerability, whether working code exists for it, and what is written about it afterwards.
Only one source knows: Exploit-DB 23133 · GitHub advisories 30 · CISA Known Exploited Vulnerabilities 1004 · Metasploit exploit modules 679 · NVD 12679 · Red Hat 19880 · Write-ups 5
Compared · what is held against what, and from which column of each source
| Property | CISA Known Exploited Vulnerabilities | Red Hat | NVD | GitHub advisories | Metasploit exploit modules | Exploit-DB | Write-ups |
|---|---|---|---|---|---|---|---|
| Cvss | not said | cvss3_score | cve.metrics.cvssMetricV31[].cvssData.baseScore | cvss.score | not said | not said | not said |
| Exploited | const:yes | not said | not said | not said | not said | not said | not said |
| Severity | not said | severity | not said | severity | not said | not said | not said |
Everything else the sources say is shown side by side, and not compared.
Found
26–50 of 729Facets
Source 99152 of 99152 claims
Severity 26286 of 99152 claims
Exploited 1731 of 99152 claims
Sources
CISA Known Exploited Vulnerabilities primary
The only source that says a vulnerability is being exploited right now.
Red Hat high
Its own severity, and the packages it tracks a vulnerability in.
NVD high
The CVSS baseline, and an anchor for CVEs the other members never reach.
GitHub advisories high
The ecosystem packages no distribution ships.
Metasploit exploit modules normal
Whether a module exists for the tool an attacker actually runs.
Exploit-DB normal
Whether working code exists at all, which is a different question from how severe it is.
Write-ups normal
The prose that explains a vulnerability after the advisories have stopped.