react-dev-utils OS Command Injection in function getProcessForPort

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2021-24033: 3.29% estimated exploitation activity in the next 30 days; percentile 88.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

react-dev-utils prior to v11.0.4 exposes a function, getProcessForPort, where an input argument is concatenated into a command string to be executed. This function is typically used from react-scripts (in Create React App projects), where the usage is safe. Only when this function is manually invoked with user-provided values (ie: by custom code) is there the potential for command injection. If you're consuming it from react-scripts then this issue does not affect you.

Published by the source

11 Mar 2021, 22:26 UTC

Last modified by the source

8 Nov 2023, 04:05 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5q6m-3h65-w53x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5q6m-3h65-w53x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-24033

Advisory: react-dev-utils OS Command Injection in function `getProcessForPort`
IDs: CVE-2021-24033, GHSA-5q6m-3h65-w53x
Record: https://patchnext.com/advisories/cve-2021-24033 (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: react-dev-utils 11.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm react-dev-utils: affected >= 0.4.0, < 11.0.4; fixed in 11.0.4

## Suggested inspection (read-only)
- `npm ls react-dev-utils --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on react-dev-utils.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5q6m-3h65-w53x (OSV record GHSA-5q6m-3h65-w53x lists affected ranges: npm react-dev-utils >=0.4.0 <11.0.4 (fixed))
- Verified: https://github.com/advisories/GHSA-5q6m-3h65-w53x (GitHub-reviewed advisory GHSA-5q6m-3h65-w53x lists affected ranges: npm react-dev-utils >=0.4.0 <11.0.4)

Commands are suggestions: review each one before running it.