NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2021-34078 — lifion-verify-deps

HIGHFix: lifion/lifion-verify-deps@be1133d

CVE-2021-34078 is a high-severity (CVSS 8.8) OS Command Injection vulnerability in lifion-verify-deps. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for lifion-verify-deps — see the affected versions and patch details below.

OS Command Injection in lifion-verify-deps

Also known asGHSA-rphm-c8gw-3r38
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk
1.91%2.51%3.11%3.71%3.2%2.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg 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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
lifion-verify-depsnpm
53downloads / week

Description

lifion-verify-dependencies through 1.1.0 is vulnerable to OS command injection via a crafted dependency name on the scanned project's package.json file.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmlifion-verify-depsall versions1.2.0npm install lifion-verify-deps@1.2.0

Affected Products

1 product · 1 configurations
Application
lifion-verifiy-dependenciesadp
< 1.2.0
range
Exploits & PoCs
1

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

lifion-verify-dependencies through 1.1.0 is vulnerable to OS command inj…

advisory.checkmarx.netNVDJun 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lifion-verify-deps, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update lifion-verify-deps to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-34078 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

lifion-verify-dependencies through 1.1.0 is vulnerable to OS command injection via a crafted dependency name on the scanned project's package.json file.
O3 Security · Impact-Aware SCA

Is CVE-2021-34078 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-34078: lifion-verify — Fixed in 1.2.0