How severe is GHSA-2m96-9w4j-wgv7?

No CVSS score has been assigned to GHSA-2m96-9w4j-wgv7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2m96-9w4j-wgv7?

GHSA-2m96-9w4j-wgv7 affects the following packages: lodash.merge (npm). Ecosystems affected: npm.

How do I fix GHSA-2m96-9w4j-wgv7?

Update lodash.merge to 4.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2m96-9w4j-wgv7 is resolved across your whole dependency graph.

How do I detect GHSA-2m96-9w4j-wgv7 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lodash.merge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2m96-9w4j-wgv7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2m96-9w4j-wgv7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2m96-9w4j-wgv7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2m96-9w4j-wgv7 published, and has it been updated?

GHSA-2m96-9w4j-wgv7 was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Prototype Pollution in lodash.mergeGHSA-2m96-9w4j-wgv7

GHSA-2m96-9w4j-wgv7 is a security vulnerability in lodash.merge. A fix is available for lodash.merge — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

7Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

lodash.mergenpm

126.4Mdownloads / week

Description

Versions of lodash.merge before 4.6.1 are vulnerable to Prototype Pollution. The function 'merge' may allow a malicious user to modify the prototype of Object via __proto__ causing the addition or modification of an existing property that will exist on all objects.

Recommendation

Update to version 4.6.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`lodash.merge`	all versions	4.6.1`npm install lodash.merge@4.6.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lodash.merge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lodash.merge to 4.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2m96-9w4j-wgv7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Versions of `lodash.merge` before 4.6.1 are vulnerable to Prototype Pollution. The function 'merge' may allow a malicious user to modify the prototype of `Object` via `__proto__` causing the addition or modification of an existing property that will exist on all objects. ## Recommendation Update to version 4.6.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-2m96-9w4j-wgv7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works