CVE-2025-11953 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in @react-native-community/cli. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-02-05) — treat it as actively exploited and patch now. A fix is available for @react-native-community/cli — see the affected versions and patch details below.
Command injection in React Native Community CLI allows remote attackers to perform remote code execution by sending HTTP requests
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-02-05. Federal agencies were required to remediate by 2026-02-26.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-11953.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-11953 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
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.
@react-native-community/clinpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @react-native-community/cli | ≥ 20.0.0-alpha.0&&< 20.0.0 | 20.0.0npm install @react-native-community/cli@20.0.0 |
| 📦npm | @react-native-community/cli | ≥ 19.0.0-alpha.0&&< 19.1.2 | 19.1.2npm install @react-native-community/cli@19.1.2 |
| 📦npm | @react-native-community/cli | ≥ 18.0.0&&< 18.0.1 | 18.0.1npm install @react-native-community/cli@18.0.1 |
| 📦npm | @react-native-community/cli-server-api | ≥ 20.0.0-alpha.0&&< 20.0.0 | 20.0.0npm install @react-native-community/cli-server-api@20.0.0 |
| 📦npm | @react-native-community/cli-server-api | ≥ 19.0.0-alpha.0&&< 19.1.2 | 19.1.2npm install @react-native-community/cli-server-api@19.1.2 |
| 📦npm | @react-native-community/cli-server-api | ≥ 18.0.0&&< 18.0.1 | 18.0.1npm install @react-native-community/cli-server-api@18.0.1 |
Affected Products
react native community clireact-native-communityResearch 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2025-11953 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
How to detect CVE-2025-11953
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-11953 -u https://target- Template
- React Native Community CLI - Unauthenticated OS Command Injection
- Severity
- critical
- Impact
- An unauthenticated attacker with network access to the bundler port can execute arbitrary programs on a developer workstation, leading to compromise of the development environment along with any source code and credentials held on it.
- Remediation
- Upgrade @react-native-community/cli-server-api to 17.0.1, 18.0.1, 19.1.2 or 20.0.0 and later, whichever is the fixed release for the line in use. Where upgrading is not immediately possible, bind the Metro development server to the loopback interface with --host 127.0.0.1 and block inbound access to the bundler port.
Template by ProjectDiscovery nuclei-templates (aryu-ru), MIT licensed. View the full template. Scan only systems you are authorised to test.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The complexity of exploitation on Linux is significantly higher than on Windows as the attacker may only trigger executable which have been pre-installed and which are accessible to the affected program.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2025-11953 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-11953 in your dependencies?
Find it across npm, including transitive dependencies.