How severe is GHSA-35jh-r3h4-6jhm?

GHSA-35jh-r3h4-6jhm has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-35jh-r3h4-6jhm?

GHSA-35jh-r3h4-6jhm affects the following packages: lodash (npm), lodash-es (npm), lodash.template (npm), lodash-template (npm), lodash-rails (RubyGems). Ecosystems affected: npm, RubyGems.

How do I fix GHSA-35jh-r3h4-6jhm?

Update lodash to 4.17.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-35jh-r3h4-6jhm is resolved across your whole dependency graph.

How do I detect GHSA-35jh-r3h4-6jhm 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-35jh-r3h4-6jhm 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-35jh-r3h4-6jhm?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-35jh-r3h4-6jhm can be triaged on real exposure rather than presence alone.

Is GHSA-35jh-r3h4-6jhm actively exploited in the wild?

Yes. There are 6 known exploit references for GHSA-35jh-r3h4-6jhm, including 6 in-the-wild exploitations 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-35jh-r3h4-6jhm?

GHSA-35jh-r3h4-6jhm has an EPSS (Exploit Prediction Scoring System) score of 21.3%, placing it in the 98th 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 warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-35jh-r3h4-6jhm?

GHSA-35jh-r3h4-6jhm is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-35jh-r3h4-6jhm?

A Nuclei detection template exists for GHSA-35jh-r3h4-6jhm, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-35jh-r3h4-6jhm published, and has it been updated?

GHSA-35jh-r3h4-6jhm was published on May 6, 2021 and was last updated on September 10, 2026. 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

HIGH severity

GHSA-35jh-r3h4-6jhm — lodash

HIGHFix: lodash/lodash@3469357

GHSA-35jh-r3h4-6jhm is a high-severity (CVSS 7.2) Code Injection vulnerability in lodash. 6 public exploit references exist, so weaponization risk is real. A fix is available for lodash — see the affected versions and patch details below.

Command Injection in lodash

Also known asCVE-2021-23337 CVE-2026-4800 GHSA-r5fr-rjxr-66jc

Published

May 6, 2021

Updated

Sep 10, 2026

Affected

5 pkgs

Patched

3 / 5

Exploits

6 known

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

EPSS Exploitation Probability

via FIRST.org ↗

21.3%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% 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.

How urgent is this, really

GHSA-35jh-r3h4-6jhm 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 378,567 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

5 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

lodash-esnpm

34.4Mdownloads / week

lodash.templatenpm

5.2Mdownloads / week

Description

lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.

Affected Packages

5 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`lodash`	all versions	4.17.21`npm install lodash@4.17.21`
📦npm	`lodash-es`	all versions	4.17.21`npm install lodash-es@4.17.21`
📦npm	`lodash.template`	all versions	No fix
📦npm	`lodash-template`	all versions	No fix
💎RubyGems	`lodash-rails`	all versions	4.17.21`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.