basicsecurity.net
Proof, not just disclosure.
Threats / React Native Community / CVE-2025-11953
CVE-2025-11953 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

React Native Community CLI vulnerability

React Native Community CLI contains an OS command injection vulnerability in the Metro Development Server that allows unauthenticated attackers to execute arbitrary commands via POST requests to a vulnerable endpoint.

Verdict

Today item — known-exploited.

Unauthenticated remote attackers can inject and execute arbitrary OS commands on systems running the affected CLI, particularly on Windows where shell command execution with controlled arguments is possible. Active exploitation has been observed.

CISA KEV Yes · 2026-02-053EPSS 0.61938 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-02-05).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.61938 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: React Native Community, CLI. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I send a crafted POST request to the exposed Metro Development Server endpoint containing injected OS commands.
Business
Development infrastructure is compromised, allowing unauthorized code execution on developer machines and build systems.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute arbitrary executables or shell commands with full argument control, particularly on Windows systems.
Business
Attackers gain ability to deploy malware, exfiltrate source code, or pivot to internal networks from compromised development environments.
3

Lateral reach — past segmentation narrative 3

Attacker
I leverage the unauthenticated nature of the endpoint to attack any system running the vulnerable CLI without credentials.
Business
Attack surface expands across all organizations using React Native Community CLI in development workflows, increasing incident response burden.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 8 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by JFROG (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by JFROGCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.