PatchTheCVECVE-2020-8149: Lack of output sanitization allowed an attack to execute arbitrary shell commands via the logkitty npm package
CVE-2020-8149 is a critical-severity flaw (CVSS 9.8) affecting logkitty. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Lack of output sanitization allowed an attack to execute arbitrary shell commands via the logkitty npm package before version 0.7.1.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 2.0% (top 19%) |
| CISA exploited list | No |
| Weakness | CWE-94 |
| Published | 2020-05-15 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-8149?
logkitty: upgrade to 0.7.1. Exact commands for each OS are on this page.
Is CVE-2020-8149 being exploited?
CVE-2020-8149 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-8149 affect?
CVE-2020-8149 affects logkitty. Severity is critical (CVSS 9.8). Lack of output sanitization allowed an attack to execute arbitrary shell commands via the logkitty npm package before version 0.7.1.
How urgent is CVE-2020-8149?
Priority 65/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action