apex-publish-static-files vulnerabilities and fixes

Q: How do I fix apex-publish-static-files vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Q: Is apex-publish-static-files being exploited right now?

None of the tracked apex-publish-static-files CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Q: Which apex-publish-static-files CVE should I patch first?

CVE-2018-16462 currently ranks highest (69/100): A command injection vulnerability in the apex-publish-static-files npm module version <2.0.1 which allows arbi.

Recent CVEs affecting apex-publish-static-files, with upgrade or downgrade steps. 1 tracked.

Also searched as: apex publish static files.

apex-publish-static-files has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-10-30. Highest priority: CVE-2018-16462 (score 69/100).

CVE-2018-16462 CRITICAL 10.0 UPGRADE A command injection vulnerability in the apex-publish-static-files npm module version <2.0.1 which allows arbi

FAQ

How do I fix apex-publish-static-files vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is apex-publish-static-files being exploited right now?

None of the tracked apex-publish-static-files CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which apex-publish-static-files CVE should I patch first?

CVE-2018-16462 currently ranks highest (69/100): A command injection vulnerability in the apex-publish-static-files npm module version <2.0.1 which allows arbi.

← Back to latest CVEs