CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HKnown 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H@react-native-community/cli (npm): fixed in 20.0.0, 19.1.2, 18.0.1@react-native-community/cli-server-api (npm): fixed in 20.0.0, 19.1.2, 18.0.1Explain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| react-native-community:react_native_community_cli | from 19.0.0 before 19.1.2 |
| react-native-community:react_native_community_cli | 18.0.0 |
| react-native-community:react_native_community_cli | 20.0.0:alpha0 |
| react-native-community:react_native_community_cli | 20.0.0:alpha1 |
| react-native-community:react_native_community_cli | 20.0.0:alpha2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-399j-vxmf-hjvr | npm | @react-native-community/cli | >=20.0.0-alpha.0 <20.0.0 | 20.0.0 |
| GHSA-399j-vxmf-hjvr | npm | @react-native-community/cli | >=19.0.0-alpha.0 <19.1.2 | 19.1.2 |
| GHSA-399j-vxmf-hjvr | npm | @react-native-community/cli | >=18.0.0 <18.0.1 | 18.0.1 |
| GHSA-399j-vxmf-hjvr | npm | @react-native-community/cli-server-api | >=20.0.0-alpha.0 <20.0.0 | 20.0.0 |
| GHSA-399j-vxmf-hjvr | npm | @react-native-community/cli-server-api | >=19.0.0-alpha.0 <19.1.2 | 19.1.2 |
| GHSA-399j-vxmf-hjvr | npm | @react-native-community/cli-server-api | >=18.0.0 <18.0.1 | 18.0.1 |
Red Hat rates this Important.
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.
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.
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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.