dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 26 Feb 2026.
React Native Community CliFramework / library · React Native Community

CVE-2025-11953

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-03
Fix available
A fix is available. Upgrade to 19.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Metro Development Server in React Native Community CLI binds to external interfaces by default and contains an OS command injection vulnerability in a POST endpoint. Unauthenticated network attackers can execute arbitrary executables and shell commands with fully controlled arguments.

MitigationRestrict Metro server binding to localhost (127.0.0.1) only, use firewall rules to block external access to the server port, or disable the development server when not actively debugging.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
React Native Community CliFramework / library
Affected:>= 19.0.0, < 19.1.2= 18.0.0= 20.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed React Native CLI version
    Run 'npx react-native --version' or check package.json dependencies for '@react-native-community/cli'
    Affected if The version matches >= 19.0.0 and < 19.1.2, equals 18.0.0, or equals 20.0.0
  2. Check Metro server binding configuration
    Examine your Metro configuration file (metro.config.js) for the 'server' section and look for the 'host' setting, or inspect runtime startup logs for the --host parameter used when starting Metro
    Affected if The server binds to '0.0.0.0' or an external IP address rather than 'localhost' or '127.0.0.1'
  3. Verify network exposure of Metro server
    When Metro is running, check which interfaces it is listening on using 'netstat -an' or 'ss -tlnp' and look for port 8081 (default Metro port) bound to non-localhost addresses
    Affected if Port 8081 (or your configured Metro port) is listening on 0.0.0.0 or an external IP rather than only 127.0.0.1
  4. Confirm CLI project configuration
    Locate the package.json in your React Native project and verify the exact version of '@react-native-community/cli' and '@react-native-community/cli-platform-ios/android' dependencies listed
    Affected if Any of these packages are at versions matching the affected range

You are affected if your React Native Community CLI version falls within the vulnerable ranges AND your Metro server is configured to bind to all network interfaces rather than localhost only.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 19.1.2 or later
Fixed in 19.1.2
Vendor patch github.com →
Interim mitigation

Restrict Metro server binding to localhost (127.0.0.1) only, use firewall rules to block external access to the server port, or disable the development server when not actively debugging.

Recommended fix High confidence

React Native Community CLI 19.1.2+ (or 20.0.1+ for 20.x branch)

  1. Upgrade React Native Community CLI to version 19.1.2 or later for the 19.x branch
  2. For version 18.0.0, upgrade to 19.1.2 or later (or to the latest 18.x stable if available)
  3. For version 20.0.0, upgrade to 20.0.1 or later
  4. After upgrading, verify the Metro server no longer binds to 0.0.0.0 by default; it should bind to localhost (127.0.0.1)
Caveat Upgrading between major versions (e.g., 18.x to 19.x) may introduce breaking changes in the React Native framework; review the migration guide for your version jump

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in React Native Community Cli Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11953 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11953 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data