GHSA-qjg4-w4c6-f6c6 is a high-severity (CVSS 7.3) CWE-77 vulnerability in mversion. O3 Security confirms whether GHSA-qjg4-w4c6-f6c6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Command injection in mversion
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.
mversionnpmDescription
Impact
This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input.
Patches
Patched by version 2.0.0. Previous releases are deprecated in npm.
Workarounds
Make sure to escape git commit messages when using the commitMessage option for the update function.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | mversion | all versions | 2.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mversion. 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 mversion to 2.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qjg4-w4c6-f6c6 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-qjg4-w4c6-f6c6 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-qjg4-w4c6-f6c6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-qjg4-w4c6-f6c6 in your dependencies?
O3 detects GHSA-qjg4-w4c6-f6c6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.