GHSA-m8r5-7wf4-63mw
CRITICALGHSA-m8r5-7wf4-63mw is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in nadesiko3. O3 Security confirms whether GHSA-m8r5-7wf4-63mw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Nadesiko3 OS Command Injection vulnerability
Blast Radius
nadesiko3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
OS command injection vulnerability in Nadesiko3 (PC Version) v3.3.68 and earlier allows a remote attacker to execute an arbitrary OS command when processing compression and decompression on the product.
Release notes for versions 3.3.62 and 3.3.69 both link to patches for this particular issue. The JPCERT/CC advisory lists versions 3.3.68 and prior as vulnerable, and the most recent patch for this issue is tagged with version 3.3.69.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | nadesiko3 | all versions | 3.3.69 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nadesiko3. 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 nadesiko3 to 3.3.69 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m8r5-7wf4-63mw 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-m8r5-7wf4-63mw 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-m8r5-7wf4-63mw. 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-m8r5-7wf4-63mw in your dependencies?
O3 detects GHSA-m8r5-7wf4-63mw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.