Summary
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.
Impact
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
CVE-2025-11953 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (20.0.0, 19.1.2, 18.0.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
@react-native-community/cli to 20.0.0 or later; @react-native-community/cli to 19.1.2 or later; @react-native-community/cli to 18.0.1 or later; @react-native-community/cli-server-api to 20.0.0 or later; @react-native-community/cli-server-api to 19.1.2 or later; @react-native-community/cli-server-api to 18.0.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-11953? CVE-2025-11953 is a critical-severity OS command injection vulnerability in @react-native-community/cli (npm), affecting versions >= 20.0.0-alpha.0, < 20.0.0. It is fixed in 20.0.0, 19.1.2, 18.0.1. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- How severe is CVE-2025-11953? CVE-2025-11953 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2025-11953?
@react-native-community/cli(npm) (versions >= 20.0.0-alpha.0, < 20.0.0)@react-native-community/cli-server-api(npm) (versions >= 20.0.0-alpha.0, < 20.0.0)
- Is there a fix for CVE-2025-11953? Yes. CVE-2025-11953 is fixed in 20.0.0, 19.1.2, 18.0.1. Upgrade to this version or later.
- Is CVE-2025-11953 exploitable, and should I be worried? Whether CVE-2025-11953 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-11953 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-11953?
- Upgrade
@react-native-community/clito 20.0.0 or later - Upgrade
@react-native-community/clito 19.1.2 or later - Upgrade
@react-native-community/clito 18.0.1 or later - Upgrade
@react-native-community/cli-server-apito 20.0.0 or later - Upgrade
@react-native-community/cli-server-apito 19.1.2 or later - Upgrade
@react-native-community/cli-server-apito 18.0.1 or later
- Upgrade