GHSA-399j-vxmf-hjvr
CRITICAL@react-native-community/cli has arbitrary OS command injection
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
@react-native-community/cli📦@react-native-community/cli📦@react-native-community/cli📦@react-native-community/cli-server-api📦@react-native-community/cli-server-api📦@react-native-community/cli-server-apiReal-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
The Metro Development Server, which is opened by the React Native CLI, binds to external interfaces by default. The server exposes an endpoint that is vulnerable to OS command injection. This allows unauthenticated network attackers to send a POST request to the server and run arbitrary executables. On Windows, the attackers can also execute arbitrary shell commands with fully controlled arguments.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @react-native-community/cli | ≥ 20.0.0-alpha.0&&< 20.0.0 | 20.0.0 |
| 📦npm | @react-native-community/cli | ≥ 19.0.0-alpha.0&&< 19.1.2 | 19.1.2 |
| 📦npm | @react-native-community/cli | ≥ 18.0.0&&< 18.0.1 | 18.0.1 |
| 📦npm | @react-native-community/cli-server-api | ≥ 20.0.0-alpha.0&&< 20.0.0 | 20.0.0 |
| 📦npm | @react-native-community/cli-server-api | ≥ 19.0.0-alpha.0&&< 19.1.2 | 19.1.2 |
| 📦npm | @react-native-community/cli-server-api | ≥ 18.0.0&&< 18.0.1 | 18.0.1 |
Research 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 @react-native-community/cli. 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 @react-native-community/cli to 20.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-399j-vxmf-hjvr 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-399j-vxmf-hjvr 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-399j-vxmf-hjvr. 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-399j-vxmf-hjvr in your dependencies?
O3 detects GHSA-399j-vxmf-hjvr across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.