Exploitation riskProbably exploitedHow this is measuredCombines four public sources, each answering a different question. CVSS (NVD) scores how bad exploitation would be. KEV (CISA) confirms exploitation is happening. EPSS (FIRST) estimates the chance of exploitation in the next 30 days. LEV (NIST CSWP 41) compounds a CVE's own EPSS history into the chance it has already been exploited. “Elevated” means EPSS at or above 10%; LEV is counted as material at 10%. LEV and EPSS are statistical estimates about a vulnerability, not findings about this vendor — and LEV is a stated lower bound, so “10%” means “at least 10%”, never “probably happened”. The underlying CVEs are matched to this vendor by name, not by exact product/version, so check each linked NVD record before drawing conclusions.
2 of 2 CVEs assessed
0
confirmed exploited
0
EPSS ≥ 10%
74%
highest single CVE
1 CVE has an estimated 10%-or-higher chance of having already been exploited despite not appearing on CISA's KEV catalog. KEV is a curated record of confirmed cases rather than a complete census, so this is where its coverage is likely thinnest — an estimate from EPSS history, not a finding. Based on a median of 3.5 EPSS observations per CVE.
Cohesity DataProtect prior to 6.8.1_u5 or 7.1 was discovered to have a incorrect access control vulnerability due to a lack of TLS Certificate Validation.
Recent changes
last 90 days
CVE-2017-2154 is now estimated at a 74% chance of having already been exploited, despite not appearing on CISA's Known Exploited Vulnerabilities catalog.2026-08-31 · NVD ↗
CVE severity over timeUI-24 — CVE severity timelineEvery known CVE with a disclosure date and severity, plotted by when it was published — lets you see whether disclosures are trending toward more or less severe, not just a raw count. Same NVD-sourced, name-matched data as the list below.
CVEs by year and severity
Count of matched CVEs by the year NVD published them.
Year
Critical
High
Medium
Low
Unscored
Total
2024
0
0
1
0
0
1
2017
0
1
0
0
0
1
Highest EPSS scores
EPSS is FIRST's estimate of the chance a CVE is exploited in the next 30 days. It measures likelihood, not impact.
Known CVEs (2)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.
Cohesity DataProtect prior to 6.8.1_u5 or 7.1 was discovered to have a incorrect access control vulnerability due to a lack of TLS Certificate Validation.
Untrusted search path vulnerability in Hanako 2017, Hanako 2016, Hanako 2015, Hanako Pro 3, JUST Office 3 [Standard], JUST Office 3 [Eco Print Package], JUST Office 3 & Tri-De DataProtect Package, JUS…
How this is counted
CVEs come from the US National Vulnerability Database (NVD) and are matched to DataProtect 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-08-31.
Known-exploited status comes from the CISA Known Exploited Vulnerabilities (KEV) catalog. Last checked: 2026-10-20.
Exploit probability (EPSS) comes from FIRST. Latest score date: 2026-10-20.
