CVE-2018-16462: A command injection vulnerability in the apex-publish-static-files npm module version <2.0.1 which allows arbi
CVE-2018-16462 is a critical-severity flaw (CVSS 10.0) affecting apex-publish-static-files. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A command injection vulnerability in the apex-publish-static-files npm module version <2.0.1 which allows arbitrary shell command execution through a maliciously crafted argument.
Why this priority
- Critical severity
- EPSS top 6%: very likely to be exploited
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
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-2018-16462?
apex-publish-static-files: upgrade to 2.0.1. Exact commands for each OS are on this page.
Is CVE-2018-16462 being exploited?
CVE-2018-16462 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-2018-16462 affect?
CVE-2018-16462 affects apex-publish-static-files. Severity is critical (CVSS 10.0). A command injection vulnerability in the apex-publish-static-files npm module version <2.0.1 which allows arbitrary shell command execution through a maliciously crafted argument.
How urgent is CVE-2018-16462?
Priority 69/100. Critical severity; EPSS top 6%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action