CVE-2019-15657: Arbitrary Code Execution in eslint-utils
Summary
CVE-2019-15657: Arbitrary Code Execution in eslint-utils. Affects eslint-utils versions >= 1.2.0, < 1.4.1. Fixed in 1.4.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The eslint-utils package is an npm package used for linting JavaScript code. It provides utility functions for ESLint plugins and rules. The package is widely used in the JavaScript development community.
Vulnerability Detail
Versions of eslint-utils >=1.2.0 or <1.4.1 are vulnerable to Arbitrary Code Execution. The vulnerability lies in the getStaticValue function, which does not properly sanitize user input. This allows attackers to supply malicious input that executes arbitrary code during the linting process. The getStringIfConstant and getPropertyName functions are not affected by this vulnerability. The vulnerability has a CVSS score of 9.8, indicating its critical severity.
How To Fix
Latest published version: 3.0.0 as of 22 Oct 2026
npm install eslint-utils@3.0.0Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.4.1
This is the first release that contains the fix.
npm install eslint-utils@1.4.1Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
The eslint-utils package is vulnerable to arbitrary code execution in versions >=1.2.0 and <1.4.1. It is crucial to upgrade to version 1.4.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for eslint-utils →
FAQ
The vulnerability allows attackers to execute arbitrary code during the linting process, which can lead to remote code execution or other malicious activities.
Versions >=1.2.0 and <1.4.1 of eslint-utils are affected by this vulnerability.
No, upgrading to version 1.4.1 or later is the recommended solution.
There is no evidence of this vulnerability being exploited in the wild at the time of this advisory.
Yes, this vulnerability has a CVSS score of 9.8, indicating its critical severity.
