dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-14802

HIGH · 7.3 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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
A vulnerability was detected in react create-react-app up to 5.0.1 on macOS. This affects the function startBrowserProcess of the file openBrowser.js of the component react-dev-utils. Performing a manipulation results in os command injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

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

OS command injection vulnerability in react-dev-utils (create-react-app up to 5.0.1) in the startBrowserProcess function of openBrowser.js on macOS. The function improperly handles input when launching the default browser, allowing remote attackers to inject and execute arbitrary OS commands through the browser opening mechanism.

MitigationUntil an official patch is released, disable or bypass the affected browser-launching functionality. If possible, upgrade to a patched version immediately. Alternatively, implement strict input validation or sandboxing around the openBrowser functionality to prevent command injection.

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

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
Low
Integrity
Low
Availability
Low

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

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 react-dev-utils installation
    Run 'npm list react-dev-utils' or check package.json dependencies for react-dev-utils
    Affected if react-dev-utils is listed as a dependency and version is 12.x or lower (pre-patch)
  2. Identify create-react-app version
    Run 'npm list create-react-app' or check the react-scripts version in package.json (react-dev-utils is a transitive dependency of react-scripts)
    Affected if create-react-app or react-scripts version is 5.0.1 or lower
  3. Confirm macOS environment
    Run 'uname -s' to verify the operating system
    Affected if System is macOS (the vulnerability specifically affects macOS)
  4. Check for openBrowser usage
    Search codebase for imports or usage of 'openBrowser' from 'react-dev-utils' (grep -r 'openBrowser' node_modules/react-dev-utils or in source files)
    Affected if The application imports or uses the openBrowser function from react-dev-utils
  5. Inspect openBrowser.js source
    Examine node_modules/react-dev-utils/openBrowser.js and locate the startBrowserProcess function
    Affected if The startBrowserProcess function exists and uses unsanitized input for browser launching (indicates vulnerability present)

Your environment is affected if react-dev-utils (or create-react-app/react-scripts up to 5.0.1) is installed on macOS and the openBrowser functionality is used, allowing unsanitized input to reach the browser launch mechanism.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until an official patch is released, disable or bypass the affected browser-launching functionality. If possible, upgrade to a patched version immediately. Alternatively, implement strict input validation or sandboxing around the openBrowser functionality to prevent command injection.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14802 — 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-2026-14802 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