How severe is GHSA-4xc9-xhrj-v574?

No CVSS score has been assigned to GHSA-4xc9-xhrj-v574 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4xc9-xhrj-v574?

GHSA-4xc9-xhrj-v574 affects the following packages: lodash (npm), lodash-rails (RubyGems). Ecosystems affected: npm, RubyGems.

How do I fix GHSA-4xc9-xhrj-v574?

Update lodash to 4.17.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4xc9-xhrj-v574 is resolved across your whole dependency graph.

How do I detect GHSA-4xc9-xhrj-v574 in my npm, RubyGems dependencies?

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.

How do I mitigate GHSA-4xc9-xhrj-v574 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-4xc9-xhrj-v574?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4xc9-xhrj-v574 can be triaged on real exposure rather than presence alone.

Is GHSA-4xc9-xhrj-v574 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-4xc9-xhrj-v574, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-4xc9-xhrj-v574?

GHSA-4xc9-xhrj-v574 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4xc9-xhrj-v574?

GHSA-4xc9-xhrj-v574 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4xc9-xhrj-v574 published, and has it been updated?

GHSA-4xc9-xhrj-v574 was published on February 7, 2019 and was last updated on August 12, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm💎 RubyGems

Not in CISA KEV

GHSA-4xc9-xhrj-v574 — lodash

Fix: lodash/lodash@90e6199

GHSA-4xc9-xhrj-v574 is a Uncontrolled Resource Consumption 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

Also known asCVE-2018-16487

Published

Feb 7, 2019

Updated

Aug 12, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

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.

Real-World Exposure

2 pkgs affected

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.

198Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

lodashnpm

128.5Mdownloads / week

Description

Versions of lodash before 4.17.11 are vulnerable to prototype pollution.

The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow 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.11 or later.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`lodash`	all versions	4.17.11`npm install lodash@4.17.11`
💎RubyGems	`lodash-rails`	all versions	4.17.11`bundle update lodash-rails --conservative`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A prototype pollution vulnerability was found in lodash <4.17.11 where t…

hackerone.comNVDSep 2020

Detection & mitigation playbook

Open-source dependency

Detect
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.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4xc9-xhrj-v574 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-4xc9-xhrj-v574 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4xc9-xhrj-v574. 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` before 4.17.11 are vulnerable to prototype pollution. The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow 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.11 or later.

O3 Security · Impact-Aware SCA

Is GHSA-4xc9-xhrj-v574 in your dependencies?

O3 Security finds GHSA-4xc9-xhrj-v574 across npm, RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works