Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

libnotify vulnerabilities and fixes

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

libnotify has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2020-02-12. Highest priority: CVE-2013-7381 (score 61/100).

FAQ

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

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

Which libnotify CVE should I patch first?

CVE-2013-7381 currently ranks highest (61/100): libnotify before 1.0.4 for Node.js allows remote attackers to execute arbitrary commands via unspecified chara.

← Back to latest CVEs