Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

happy vulnerabilities and fixes

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

happy has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2014-10-19. Highest priority: CVE-2014-7075 (score 35/100).

FAQ

How do I fix happy 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 happy being exploited right now?

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

Which happy CVE should I patch first?

CVE-2014-7075 currently ranks highest (35/100): The HAPPY (aka com.tw.knowhowdesign.sinfonghuei) application 2.0 for Android does not verify X.509 certificate.

← Back to latest CVEs