CVE-2025-11953
React Native Community CLI OS Command Injection
- Published3 Nov 2025
- Added to CISA KEV5 Feb 2026
- Remediation due26 Feb 2026
Description
The Metro Development Server, which is opened by the React Native Community 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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://github.com/react-native-community/cli/commit/15089907d1f1301b22c72d7f68846a2ef20df547
- https://jfrog.com/blog/cve-2025-11953-critical-react-native-community-cli-vulnerability
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-11953
- https://www.vulncheck.com/blog/metro4shell_eitw
- https://x.com/SzymonRybczak/status/1986199665000566848
- https://x.com/thymikee/status/1986770875954475375
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-11953 being actively exploited?
Yes. CVE-2025-11953 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 5 Feb 2026.
How severe is CVE-2025-11953?
CVE-2025-11953 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 94.0% probability of exploitation.
Which products are affected by CVE-2025-11953?
Affected products include React-native-community React Native Community Cli.
How do I fix CVE-2025-11953?
Upgrade affected software to a fixed version, for example React-native-community React Native Community Cli 19.1.2 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-11953 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.