How severe is CVE-2025-11953?

CVE-2025-11953 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-11953?

CVE-2025-11953 affects the following packages: @react-native-community/cli (npm), @react-native-community/cli (npm), @react-native-community/cli (npm), @react-native-community/cli-server-api (npm), @react-native-community/cli-server-api (npm), @react-native-community/cli-server-api (npm). Ecosystems affected: npm.

How do I fix CVE-2025-11953?

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.

How do I detect CVE-2025-11953 in my npm dependencies?

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.

How do I mitigate CVE-2025-11953 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2025-11953?

O3 pinpoints whether CVE-2025-11953 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-11953 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2025-11953, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-11953?

CVE-2025-11953 has an EPSS (Exploit Prediction Scoring System) score of 62.4%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-11953 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-11953 (React Native Community CLI OS Command Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-02-05. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-02-26. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-11953?

CVE-2025-11953 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-11953 published, and has it been updated?

CVE-2025-11953 was published on November 3, 2025 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-02-05 — agencies required to remediate by 2026-02-26

📦 npm

CVE-2025-11953

CRITICAL

Command injection in React Native Community CLI allows remote attackers to perform remote code execution by sending HTTP requests

Also known asGHSA-399j-vxmf-hjvr

Published

Nov 3, 2025

Updated

Jul 15, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

62.4%probability of exploitation in next 30 days

High Risk99th percentile0.00%

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

6 pkgs affected

📦@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-api

Real-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 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

6 total 6 fixed

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

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

SaidBenaissa/cve-2025-11953-vulnerability-demo

CVE-2025-11953 demonstration: Critical RCE vulnerability in React Native

⭐ 4🍴 1Feb 2026

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2025-11953 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 CVE-2025-11953 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 CVE-2025-11953. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-11953 in your dependencies?

O3 detects CVE-2025-11953 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works