lodash vulnerabilities
Lodash modular utilities.
- Registry
- npm
- Latest
- 4.18.1
- License
- MIT
10 known advisories
The latest version, 4.18.1, is not affected by any of them. Projects on older versions may be.
npm install lodash@4.18.1Security advisories for lodash
lodash vulnerable to Code Injection via `_.template` imports key names
- Affected
- >=4.0.0 <4.18.0
- Fixed in
- 4.18.0
lodash vulnerable to Prototype Pollution via array path bypass in `_.unset` and `_.omit`
- Affected
- <4.18.0
- Fixed in
- 4.18.0
Lodash has Prototype Pollution Vulnerability in `_.unset` and `_.omit` functions
- Affected
- >=4.0.0 <4.17.23
- Fixed in
- 4.17.23
Regular Expression Denial of Service (ReDoS) in lodash
- Affected
- >=4.0.0 <4.17.21
- Fixed in
- 4.17.21
Command Injection in lodash
- Affected
- <4.17.21
- Fixed in
- 4.17.21
Prototype Pollution in lodash
- Affected
- >=3.7.0 <4.17.19
- Fixed in
- 4.17.19
Regular Expression Denial of Service (ReDoS) in lodash
- Affected
- >=4.7.0 <4.17.11
- Fixed in
- 4.17.11
Prototype Pollution in lodash
- Affected
- <4.17.12
- Fixed in
- 4.17.12
Prototype Pollution in lodash
- Affected
- <4.17.11
- Fixed in
- 4.17.11
Prototype Pollution in lodash
- Affected
- <4.17.5
- Fixed in
- 4.17.5
Which of your client projects still run an old lodash?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.