CVE-2021-44906
CRITICALCVE-2021-44906 is a critical-severity (CVSS 9.8) vulnerability in minimist. 4 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2021-44906 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prototype Pollution in minimist
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.
minimistnpmDescription
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | minimist | ≥ 1.0.0&&< 1.2.6 | 1.2.6 |
| 📦npm | minimist | all versions | 0.2.4 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js,…
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js,…
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js,…
Minimist <=1.2.5 is vulnerable to Prototype Pollution via file index.js,…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for minimist. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update minimist to 1.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-44906 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 pinpoints whether CVE-2021-44906 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2021-44906. 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.
As minimist is an argument parsing module for nodejs, exploitation of this vulnerability requires an attacker to influence which arguments are passed to nodejs when running a script. Red Hat products and services are designed in such a way that gaining this ability is not trivial. Additionally, the impact is limited…
Frequently Asked Questions
Is CVE-2021-44906 in your dependencies?
O3 detects CVE-2021-44906 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.