CVE-2017-1000219: npm/KyleRoss windows-cpu all versions vulnerable to command injection resulting in code execution as Node.js u

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2017-1000219 is a critical-severity flaw (CVSS 9.8) affecting windows-cpu. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

npm/KyleRoss windows-cpu all versions vulnerable to command injection resulting in code execution as Node.js user

Why this priority

Critical severity
EPSS top 9%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	4.2% (top 9%)
CISA exploited list	No
Weakness	CWE-78
Published	2017-11-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: windows-cpu project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-11-17 00:29 UTCPublished CVE record published
2026-06-17 00:58 UTCUpdated Record last modified

windows-cpu project windows-cpu DOWNGRADE

Affected: 0.1.1 · 0.1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.1.1

1. Check installed version

apt-cache policy windows-cpu || rpm -q windows-cpu || windows-cpu --version

2. No fixed release: DOWNGRADE to a release before 0.1.1 (Debian / Ubuntu)

apt-cache madison windows-cpu sudo apt install windows-cpu=<VERSION_BEFORE_0.1.1> sudo apt-mark hold windows-cpu

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list windows-cpu sudo dnf downgrade windows-cpu-<VERSION_BEFORE_0.1.1> sudo dnf versionlock add windows-cpu

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-2017-1000219?

windows-cpu: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-1000219 being exploited?

CVE-2017-1000219 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-2017-1000219 affect?

CVE-2017-1000219 affects windows-cpu. Severity is critical (CVSS 9.8). npm/KyleRoss windows-cpu all versions vulnerable to command injection resulting in code execution as Node.js user

How urgent is CVE-2017-1000219?

Priority 67/100. Critical severity; EPSS top 9%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities · Windows vulnerabilities

References

← Back to latest CVEs