GHSA-xxjr-mmjv-4gpg is a medium-severity (CVSS 6.5) CWE-1321 vulnerability in lodash. A fix is available for lodash — see the affected versions and patch details below.
Lodash has Prototype Pollution Vulnerability in `_.unset` and `_.omit` functions
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xxjr-mmjv-4gpg.
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-xxjr-mmjv-4gpg 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-amdnpmDescription
Impact
Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes.
The issue permits deletion of properties but does not allow overwriting their original behavior.
Patches
This issue is patched on 4.17.23.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | lodash | ≥ 4.0.0&&< 4.17.23 | 4.17.23npm install lodash@4.17.23 |
| 📦npm | lodash.unset | ≥ 4.0.0 | No fix |
| 📦npm | lodash-es | ≥ 4.0.0&&< 4.17.23 | 4.17.23npm install lodash-es@4.17.23 |
| 📦npm | lodash-amd | ≥ 4.0.0&&< 4.17.23 | 4.17.23npm install lodash-amd@4.17.23 |
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.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xxjr-mmjv-4gpg 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-xxjr-mmjv-4gpg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xxjr-mmjv-4gpg. 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.
This issue is only exploitable by applications using the _.unset and _.omit functions on an object and allowing user input to determine the path of the property to be removed. This issue only allows the deletion of properties but does not allow overwriting their behavior, limiting the impact to a denial of service.…
| Product | Fixed in | Advisory |
|---|---|---|
| Cryostat 4 on RHEL 9 | cryostat/cryostat-openshift-console-plugin-rhel9:4.1.0-17 | RHSA-2026:1845 |
| HawtIO HawtIO 4.4.0 | io.hawt-project | RHSA-2026:25089 |
| Red Hat Ansible Automation Platform 2.6 for RHEL 9 | automation-platform-ui-0:2.6.6-1.el9ap | RHSA-2026:3958 |
| Red Hat Data Grid 8.6.0 | org.infinispan-infinispan-console | RHSA-2026:4630 |
| Red Hat Enterprise Linux 10 | pcs-0:0.12.1-1.el10_1.2 | RHSA-2026:2438 |
| Red Hat Enterprise Linux 10 | linux-sgx-0:2.26-7.el10 | RHSA-2026:18480 |
| Red Hat Enterprise Linux 10 | cockpit-image-builder-0:94.3-1.el10_2 | RHSA-2026:24331 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | pcs-0:0.12.0-3.el10_0.4 | RHSA-2026:2818 |
Frequently Asked Questions
Is GHSA-xxjr-mmjv-4gpg in your dependencies?
O3 Security finds GHSA-xxjr-mmjv-4gpg across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.