cve.bz

CVE-2025-11953 (Metro4Shell) React Native Community CLI OS Command Injection Vulnerability

9.8 criticalKEVExploit referenceEPSS 94%Fix available

Known as Metro4Shell

Critical (9.8) in React Native Community CLI. In CISA KEV since 2026-02-05. EPSS 94% estimated probability of exploitation activity in the next 30 days. Fixed in @react-native-community/cli 18.0.1, 19.1.2, 20.0.0.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
94% (unchanged from 94% a week ago; 94% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-02-05, due 2026-02-26
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-02-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-11953 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-11953?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-11953?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-11953 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
react-native-community:react_native_community_clifrom 19.0.0 before 19.1.2
react-native-community:react_native_community_cli18.0.0
react-native-community:react_native_community_cli20.0.0:alpha0
react-native-community:react_native_community_cli20.0.0:alpha1
react-native-community:react_native_community_cli20.0.0:alpha2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-399j-vxmf-hjvrnpm@react-native-community/cli>=20.0.0-alpha.0 <20.0.020.0.0
GHSA-399j-vxmf-hjvrnpm@react-native-community/cli>=19.0.0-alpha.0 <19.1.219.1.2
GHSA-399j-vxmf-hjvrnpm@react-native-community/cli>=18.0.0 <18.0.118.0.1
GHSA-399j-vxmf-hjvrnpm@react-native-community/cli-server-api>=20.0.0-alpha.0 <20.0.020.0.0
GHSA-399j-vxmf-hjvrnpm@react-native-community/cli-server-api>=19.0.0-alpha.0 <19.1.219.1.2
GHSA-399j-vxmf-hjvrnpm@react-native-community/cli-server-api>=18.0.0 <18.0.118.0.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-11953.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • boroeurnprach/CVE-2025-11953-PoC Harbor Check: matches CVE 0 stars, JavaScript, created
    CVE-2025-11953 - The React Native Metro server's default external binding exposes a vulnerable endpoint, allowing unauthenticated attackers…
  • Mr-In4inci3le/CVE-2025-11953-POC- Harbor Check: matches CVE 0 stars, JavaScript, created
    CVE-2025-11953 is a critical Remote Code Execution (RCE) vulnerability in the React Native CLI's Metro development server

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON