Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

hashover vulnerabilities and fixes

Recent CVEs affecting hashover, with upgrade or downgrade steps. 1 tracked.

hashover has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-03-02. Highest priority: CVE-2017-6395 (score 34/100).

FAQ

How do I fix hashover vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is hashover being exploited right now?

None of the tracked hashover CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which hashover CVE should I patch first?

CVE-2017-6395 currently ranks highest (34/100): An issue was discovered in HashOver 2.0.

← Back to latest CVEs