CVE-2022-21186 is a critical-severity (CVSS 9.8) remote code execution vulnerability in @acrontum/filesystem-template. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @acrontum/filesystem-template — see the affected versions and patch details below.
Arbitrary Command Injection
EPSS Exploitation Probability
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
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@acrontum/filesystem-templatenpmDescription
The package @acrontum/filesystem-template before 0.0.2 are vulnerable to Arbitrary Command Injection due to the fetchRepo API missing sanitization of the href field of external input.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @acrontum/filesystem-template | all versions | 0.0.2npm install @acrontum/filesystem-template@0.0.2 |
Affected Products
filesystem-templateacrontumResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @acrontum/filesystem-template, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @acrontum/filesystem-template to 0.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-21186 is resolved across your whole dependency graph.
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
Is CVE-2022-21186 in your dependencies?
Find it across npm, including transitive dependencies.