GHSA-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. A fix is available for lodash — see the affected versions and patch details below.
Prototype Pollution in lodash
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-p6mc-m468-83gw plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
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.19npm install lodash@4.17.19 |
| 📦npm | lodash-es | ≥ 3.7.0&&< 4.17.20 | 4.17.20npm install lodash-es@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p6mc-m468-83gw can be triaged on real exposure rather than presence alone.
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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
In OpenShift ServiceMesh (OSSM), Red Hat OpenShift Jaeger (RHOSJ) and Red Hat OpenShift Container Platform (RHOCP), the affected containers are behind OpenShift OAuth authentication. This restricts access to the vulnerable nodejs-lodash library to authenticated users only, therefore the impact is low. Red Hat…
| Product | Fixed in | Advisory |
|---|---|---|
| Jaeger-1.17 | distributed-tracing/jaeger-agent-rhel7:1.17.6-1 | RHSA-2020:3370 |
| Openshift Service Mesh 1.1 | kiali-0:v1.12.10.redhat2-1.el7 | RHSA-2020:3369 |
| Red Hat OpenShift Container Platform 4.6 | openshift4/ose-metering-presto:v4.6.0-202010200139.p0 | RHSA-2020:4298 |
| Red Hat Quay 3 | quay/quay-rhel8:v3.6.0-62 | RHSA-2021:3917 |
| Red Hat Virtualization 4 for Red Hat Enterprise Linux 8 | cockpit-ovirt-0:0.14.15-1.el8ev | RHSA-2020:5611 |
| Red Hat Virtualization Engine 4.4 | ovirt-engine-ui-extensions-0:1.2.3-1.el8ev | RHSA-2020:3807 |
| Red Hat Virtualization Engine 4.4 | org.ovirt.engine-root-0:4.4.3.8-1 | RHSA-2020:5179 |
Frequently Asked Questions
Is GHSA-p6mc-m468-83gw in your dependencies?
O3 Security finds GHSA-p6mc-m468-83gw across npm, RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.