GHSA-p6mc-m468-83gw
HIGHGHSA-p6mc-m468-83gw is a high-severity (CVSS 7.4) CWE-770 vulnerability in lodash. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-p6mc-m468-83gw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prototype Pollution in lodash
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
lodashnpmlodash-esnpmlodash.picknpmDescription
Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions pick, set, setWith, update, updateWith, and zipObjectDeep allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.
This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | lodash | ≥ 3.7.0&&< 4.17.19 | 4.17.19 |
| 📦npm | lodash-es | ≥ 3.7.0&&< 4.17.20 | 4.17.20 |
| 📦npm | lodash.pick | ≥ 4.0.0 | No fix |
| 📦npm | lodash.set | ≥ 3.7.0 | No fix |
| 📦npm | lodash.setwith | all versions | No fix |
| 📦npm | lodash.update | all versions | No fix |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lodash. 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 to 4.17.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p6mc-m468-83gw 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-p6mc-m468-83gw 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-p6mc-m468-83gw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p6mc-m468-83gw in your dependencies?
O3 detects GHSA-p6mc-m468-83gw across npm, RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.