Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Command Execution in windows-cpu

CVE-2017-1000219GHSA-63m4-fhf2-cmf7

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (windows-cpu 0.1.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2017-1000219: 4.24% estimated exploitation activity in the next 30 days; percentile 91.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Version of windows-cpu before 0.1.5 will execute arbitrary code passed into the first argument of the findLoad method, resulting in remote code execution. Proof of Concept Recommendation Update to version 0.1.5 or later.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-63m4-fhf2-cmf7

  2. Revision 1 · created ·

    Published from osv record GHSA-63m4-fhf2-cmf7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2017-1000219

Advisory: Command Execution in windows-cpu
IDs: CVE-2017-1000219, GHSA-63m4-fhf2-cmf7
Record: https://patchnext.com/advisories/cve-2017-1000219 (revision 2, source checked 26 Oct 2026, 12:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: windows-cpu 0.1.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm windows-cpu: affected < 0.1.5; fixed in 0.1.5

## Suggested inspection (read-only)
- `npm ls windows-cpu --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on windows-cpu.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-63m4-fhf2-cmf7 (OSV record GHSA-63m4-fhf2-cmf7 lists affected ranges: npm windows-cpu >=0 <0.1.5 (fixed))
- Verified: https://github.com/advisories/GHSA-63m4-fhf2-cmf7 (GitHub-reviewed advisory GHSA-63m4-fhf2-cmf7 lists affected ranges: npm windows-cpu >=0 <0.1.5)

Commands are suggestions: review each one before running it.

Loading voting…