How severe is GHSA-m2fc-9h5m-29cm?

GHSA-m2fc-9h5m-29cm has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-m2fc-9h5m-29cm?

GHSA-m2fc-9h5m-29cm affects the following packages: @acrontum/filesystem-template (npm). Ecosystems affected: npm.

How do I fix GHSA-m2fc-9h5m-29cm?

Update @acrontum/filesystem-template to 0.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2fc-9h5m-29cm is resolved across your whole dependency graph.

How do I detect GHSA-m2fc-9h5m-29cm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @acrontum/filesystem-template. 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.

How do I mitigate GHSA-m2fc-9h5m-29cm 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-m2fc-9h5m-29cm?

O3 pinpoints whether GHSA-m2fc-9h5m-29cm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m2fc-9h5m-29cm actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-m2fc-9h5m-29cm, including 1 in-the-wild exploitation 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.

When was GHSA-m2fc-9h5m-29cm published, and has it been updated?

GHSA-m2fc-9h5m-29cm was published on August 6, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-m2fc-9h5m-29cm

CRITICAL

GHSA-m2fc-9h5m-29cm is a critical-severity (CVSS 9.8) remote code execution vulnerability in @acrontum/filesystem-template. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-m2fc-9h5m-29cm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

@acrontum/filesystem-template vulnerable to Command Injection due to fetchRepo API missing sanitization

Also known asCVE-2022-21186

Published

Aug 6, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@acrontum/filesystem-templatenpm

26downloads / week

Description

The package @acrontum/filesystem-template before 0.0.2 is vulnerable to Arbitrary Command Injection due to the fetchRepo API missing sanitization of the href field of external input.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@acrontum/filesystem-template`	all versions	0.0.2

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.

The package @acrontum/filesystem-template before 0.0.2 are vulnerable to…

security.snyk.ioNVDAug 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @acrontum/filesystem-template. 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 @acrontum/filesystem-template to 0.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m2fc-9h5m-29cm 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 GHSA-m2fc-9h5m-29cm 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 GHSA-m2fc-9h5m-29cm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package @acrontum/filesystem-template before 0.0.2 is vulnerable to Arbitrary Command Injection due to the fetchRepo API missing sanitization of the href field of external input.

O3 Security · Impact-Aware SCA

Is GHSA-m2fc-9h5m-29cm in your dependencies?

O3 detects GHSA-m2fc-9h5m-29cm across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works