PatchTheCVECVE-2017-16063: node-opensl was a malicious module published with the intent to hijack environment variables
CVE-2017-16063 is a high-severity flaw (CVSS 7.5) affecting node-opensl. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
node-opensl was a malicious module published with the intent to hijack environment variables. It has been unpublished by npm.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
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-2017-16063?
node-opensl: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2017-16063 being exploited?
CVE-2017-16063 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-16063 affect?
CVE-2017-16063 affects node-opensl. Severity is high (CVSS 7.5). node-opensl was a malicious module published with the intent to hijack environment variables. It has been unpublished by npm.
How urgent is CVE-2017-16063?
Priority 48/100. High severity; Remotely exploitable, no login, no user action