LiveActive security incident?Get immediate response
CVE Record

CVE-2025-11953: Command injection in React Native Community CLI allows remote attackers to perform remote code execution by sending HTTP requests

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.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

A critical flaw in the React Native developer tool (Metro, started by the React Native Community CLI) lets anyone on the network run commands on a developer's computer without logging in. Because the tool listens on all network interfaces by default, attackers on the same Wi-Fi or with internet access to the port can take over the machine. It is a tooling problem, not a flaw in shipped mobile apps, but a compromised developer can leak source code, credentials, or signing keys.

Executive priority

Treat as urgent for any team building React Native apps. Inventory developer machines and CI runners, apply the patched CLI, and confirm Metro is not exposed beyond localhost.

Technical view

The Metro development server launched by the React Native Community CLI (@react-native-community/cli-server-api 4.8.0) binds to all interfaces and exposes an HTTP endpoint that passes attacker-controlled input into an OS command path (CWE-78). An unauthenticated POST allows execution of arbitrary executables on Linux and macOS, and full shell command execution with controlled arguments on Windows. CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects the unauthenticated, network-adjacent attack surface.

Likely exposure

Exposure is concentrated on developer workstations, build agents, and CI runners that start Metro via the React Native Community CLI. Risk increases sharply on shared networks, coffee-shop Wi-Fi, cloud dev environments, or any host where the dev port is reachable beyond localhost. Production servers are not directly affected, but a compromised dev box can pivot into source code, secrets, and signing material.

Exploitation context

VulnCheck publicly reports exploitation activity targeting exposed Metro servers; CISA KEV does not list this CVE at the time of analysis. The flaw is unauthenticated, network-reachable, and trivially scriptable, so any developer machine or CI host with Metro reachable on the LAN or internet should be treated as opportunistically targeted.

Researcher notes

CWE-78 OS command injection in a Metro endpoint reachable over HTTP without authentication. CVSS 9.8 (AV:N/AC:L/PR:N/UI:N) reflects the unauthenticated network reach. The advisory bundle lists @react-native-community/cli-server-api 4.8.0; consult the JFrog write-up and the upstream commit for exact affected ranges and the fixed version. VulnCheck's metro4shell_eitw post indicates observed exploitation; CISA KEV does not list this CVE in the bundle. Windows hosts are noted as more dangerous because attackers can fully control shell arguments.

Mitigation direction

  • Upgrade @react-native-community/cli-server-api past the patched commit referenced in the React Native Community CLI repository.
  • Bind Metro to localhost only and block external access to its dev port at the host firewall.
  • Avoid running Metro on untrusted networks until the patched CLI is in use.
  • Audit CI and cloud development environments for exposed Metro instances and shut down stale processes.
  • Follow vendor guidance from React Native Community CLI for any version-specific upgrade notes.

Validation and detection

  • Inventory hosts running React Native Community CLI and capture the installed @react-native-community/cli-server-api version.
  • Check whether Metro is listening on a non-loopback interface using netstat or lsof on the dev host.
  • Confirm package.json or lockfiles resolve to a patched cli-server-api version after upgrade.
  • Review proxy, EDR, or network logs for unsolicited POST requests to the Metro dev port.
  • Reproduce only in an isolated lab and consult the JFrog and upstream commit references for indicators.
Prepared
Reviewed
Confidence
high
Sources
6

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-11953 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-11953Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendor@react-native-community/cli-server-api@react-native-community/cli-server-api, 4.8.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.