Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

logkitty vulnerabilities and fixes

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

logkitty has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2020-05-15. Highest priority: CVE-2020-8149 (score 65/100).

FAQ

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

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

Which logkitty CVE should I patch first?

CVE-2020-8149 currently ranks highest (65/100): Lack of output sanitization allowed an attack to execute arbitrary shell commands via the logkitty npm package.

← Back to latest CVEs