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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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.

How does O3 Security protect against GHSA-2m96-9w4j-wgv7?

O3 pinpoints whether GHSA-2m96-9w4j-wgv7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-2m96-9w4j-wgv7

GHSA-2m96-9w4j-wgv7 is a security vulnerability in lodash.merge. O3 Security confirms whether GHSA-2m96-9w4j-wgv7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Prototype Pollution in lodash.merge

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

📦lodash.merge

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether GHSA-2m96-9w4j-wgv7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2m96-9w4j-wgv7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-2m96-9w4j-wgv7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works