npm vulnerability intelligence

lodash.merge NPM Package
Vulnerability Check

The Lodash method `_.merge` exported as a module.

High severity MIT v4.6.2
Vulnerability Analysis OSV Live

lodash.merge

v4.6.2 · MIT · 105,446,238 dl/wk

Advisory Breakdown

Critical 0
High 2
Moderate 0
Low 0

Severity Rating

High severity

2 advisories

High severity

Weekly downloads

105,446,238

Total advisories

2

Latest version

4.6.2

License

MIT

Advisories Package Info Runtime

Known advisories

OSV records for the npm ecosystem

2
GHSA-2m96-9w4j-wgv7 high

Prototype Pollution in lodash.merge

Affected: >=0 <4.6.1 Fixed in: 4.6.1 Updated Aug 31, 2020
View source
GHSA-h726-x36v-rx45 high

Prototype Pollution in lodash.merge

Affected: >=0 <4.6.2 Fixed in: 4.6.2 Updated Aug 31, 2020
View source

Checked Jun 7, 2026, 5:12 PM from npm and OSV.dev

Package metadata

From the npm registry

Package name
lodash.merge
Ecosystem
npm
Latest version
4.6.2
License
MIT
Weekly downloads
105,446,238
Repository
Open repository

Remediation boundary

What RequestGuard does — and doesn't — cover

RequestGuard does not fix npm package vulnerabilities. Dependency remediation happens through package updates, patches, lockfile changes, and maintainer guidance. RequestGuard can help mitigate runtime abuse around exposed web and API flows while remediation is handled separately.

Signup flows
Login attempts
API traffic

Protect runtime flows →

Allow, challenge, review, and block decisions for exposed endpoints.

Data from npm registry and OSV.dev · Checked 6/7/2026, 5:12:22 PM