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 version 4.17.21 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

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 2.4%, placing it in the 85th 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-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 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

GHSA-35jh-r3h4-6jhm

HIGH

Command Injection in lodash

Also known asCVE-2021-23337

Published

May 6, 2021

Updated

Aug 12, 2025

Affected

5 pkgs

Patched

3 / 5

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk85th percentile-1.91%

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.

Blast Radius

5 pkgs affected

📦lodash📦lodash-es📦lodash.template📦lodash-template💎lodash-rails

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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	`lodash-es`	all versions	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

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.