Count of matched CVEs by the year NVD published them.
Year
Critical
High
Medium
Low
Unscored
Total
2026
0
0
0
0
1
1
Known CVEs (1)About this listSourced from the public NVD database, matched by vendor name. This is a name-based match, not exact version tracking — always check the linked NVD record for affected versions before drawing conclusions. “New” means published within the last 30 days. “Actively exploited” means CISA's Known Exploited Vulnerabilities (KEV) catalog confirms real-world exploitation, not just a theoretical severity score. An “EPSS” chip appears at 10% and above: that is FIRST's estimated chance of exploitation in the next 30 days, which measures likelihood rather than impact and so can differ sharply from the severity beside it. See the Exploitation risk panel above for the full picture.
Rejected reason: Red Hat Product Security has come to the conclusion that this CVE is false due to upstream security policy.
How this is counted
CVEs come from the US National Vulnerability Database (NVD) and are matched to Upstream Security by vendor name. A name match can include CVEs that concern a similarly named product, and can miss ones filed under another name. The count reflects how widely a vendor's software is deployed and examined as much as anything else, so it is not a measure of how secure the vendor is and should not be used to rank vendors. Latest CVE added here: 2026-09-06.
Known-exploited status comes from the CISA Known Exploited Vulnerabilities (KEV) catalog. Last checked: 2026-10-21.
Exploit probability (EPSS) comes from FIRST. Latest score date: not yet recorded.
