GHSA-jf85-cpcp-j695
CRITICALGHSA-jf85-cpcp-j695 is a critical-severity (CVSS 9.1) CWE-1321 vulnerability in lodash. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-jf85-cpcp-j695 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-amdnpmDescription
Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Recommendation
Update to version 4.17.12 or later.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | lodash | all versions | 4.17.12 |
| 📦npm | lodash-es | all versions | 4.17.14 |
| 📦npm | lodash-amd | all versions | 4.17.13 |
| 📦npm | lodash.defaultsdeep | all versions | 4.6.1 |
| 💎RubyGems | lodash-rails | all versions | 4.17.12 |
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.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jf85-cpcp-j695 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-jf85-cpcp-j695 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-jf85-cpcp-j695. 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-jf85-cpcp-j695 in your dependencies?
O3 detects GHSA-jf85-cpcp-j695 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.