🚨 [security] Update @react-native-community/cli 19.1.1 → 20.2.0 (major)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​react-native-community/cli (19.1.1 → 20.2.0) · Repo · Changelog

Security Advisories 🚨

🚨 @react-native-community/cli has arbitrary OS command injection

The Metro Development Server, which is opened by the React Native 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.

🚨 @react-native-community/cli has arbitrary OS command injection

The Metro Development Server, which is opened by the React Native 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.

Release Notes

20.2.0

More info than we can show here.

20.1.1

More info than we can show here.

20.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

✳️ debug (4.4.1 → 4.4.3) · Repo · Changelog

Security Advisories 🚨

🚨 debug@4.4.2 contains malware after npm account takeover

Impact

On 8 September 2025, the npm publishing account for debug was taken over after a phishing attack. Version 4.4.2 was published, functionally identical to the previous patch version, but with a malware payload added attempting to redirect cryptocurrency transactions to the attacker's own addresses from within browser environments.

Local environments, server environments, command line applications, etc. are not affected. If the package was used in a browser context (e.g. a direct <script> inclusion, or via a bundling tool such as Babel, Rollup, Vite, Next.js, etc.) there is a chance the malware still exists and such bundles will need to be rebuilt.

The malware seemingly only targets cryptocurrency transactions and wallets such as MetaMask. See references below for more information on the payload.

Patches

npm removed the offending package from the registry over the course of the day on 8 September, preventing further downloads from npm proper.

On 13 September, the package owner published new patch versions to help cache-bust those using private registries who might still have the compromised version cached. This version is functionally identical to the previously known-good version, published as a patch version bump above the compromised version.

Users should upgrade to the latest patch version, completely remove their node_modules directory, clean their package manager's global cache, and rebuild any browser bundles from scratch.

Those operating private registries or registry mirrors should purge the offending versions from any caches.

References

• https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised
• https://socket.dev/blog/npm-author-qix-compromised-in-major-supply-chain-attack
• https://www.ox.security/blog/npm-packages-compromised/

Point of Contact

In the event suspicious behavior is still observed for the package listed in this security advisory after performing all of the above cleaning operations (see Patches above), please reach out via one of the following channels of communication:

• Bluesky, package owner: https://bsky.app/profile/bad-at-computer.bsky.social
• debug repository, tracking issue (applies to all packages affected in the breach): #1005

Release Notes

4.4.3

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​react-native-community/cli-platform-android (indirect, 19.1.1 → 20.2.0) · Repo · Changelog

Release Notes

20.2.0

More info than we can show here.

20.1.1

More info than we can show here.

20.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​react-native-community/cli-platform-ios (indirect, 19.1.1 → 20.2.0) · Repo · Changelog

Release Notes

20.2.0

More info than we can show here.

20.1.1

More info than we can show here.

20.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​react-native-community/cli-server-api (indirect, 19.1.1 → 20.2.0) · Repo · Changelog

Security Advisories 🚨

🚨 @react-native-community/cli has arbitrary OS command injection

The Metro Development Server, which is opened by the React Native 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.

🚨 @react-native-community/cli has arbitrary OS command injection

The Metro Development Server, which is opened by the React Native 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.

Release Notes

20.2.0

More info than we can show here.

20.1.1

More info than we can show here.

20.1.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ dayjs (indirect, 1.11.13 → 1.11.21) · Repo · Changelog

Release Notes

1.11.21

More info than we can show here.

1.11.20

More info than we can show here.

1.11.19

More info than we can show here.

1.11.18

More info than we can show here.

1.11.17

More info than we can show here.

1.11.16

More info than we can show here.

1.11.15

More info than we can show here.

1.11.14

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ errorhandler (indirect, 1.5.1 → 1.5.2) · Repo · Changelog

Release Notes

1.5.2

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ joi (indirect, 17.13.3 → 17.13.4) · Repo · Changelog

Security Advisories 🚨

🚨 joi has an uncaught RangeError on deeply nested input through recursive `link()` schemas

Impact

Denial of service via untrapped exception in services validating user-supplied JSON / object input with recursive link schemas.

The blast radius depends on how the application invokes joi:

• Highest impact: validate() called without try/catch in a request handler would cause an unhandled exception, potentially crashing the process.
• Lower impact: validateAsync() or validate() inside a try/catch, the validation fails, but the error type is RangeError rather than a structured ValidationError, complicating error handling.

Patches

Upgrade to version >= 18.2.1.

Workarounds

Try/catch the validation to avoid uncaught exceptions.

References

• Pull request: #3113

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ side-channel (indirect, 1.1.0 → 1.1.1) · Repo · Changelog

Release Notes

1.1.1 (from changelog)

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ side-channel-list (indirect, 1.0.0 → 1.0.1) · Repo · Changelog

Release Notes

1.0.1 (from changelog)

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 @​nodable/entities (added, 2.2.0)

🆕 anynum (added, 1.0.1)

🆕 fast-xml-builder (added, 1.2.0)

🆕 is-unsafe (added, 1.0.1)

🆕 path-expression-matcher (added, 1.6.1)

🆕 xml-naming (added, 0.1.0)

🆕 semver (added, 7.8.5)

🆕 ws (added, 6.2.4)

🆕 body-parser (added, 2.3.0)

🆕 iconv-lite (added, 0.7.2)

🆕 qs (added, 6.15.3)

🆕 content-type (added, 2.0.0)

🆕 statuses (added, 2.0.2)

🆕 fast-xml-parser (added, 5.9.3)

🆕 http-errors (added, 2.0.1)

🆕 media-typer (added, 1.1.0)

🆕 mime-db (added, 1.54.0)

🆕 mime-types (added, 3.0.2)

🆕 raw-body (added, 3.0.2)

🆕 strnum (added, 2.4.1)

🆕 type-is (added, 2.1.0)

🗑️ @​jest/types (removed)

🗑️ @​types/yargs (removed)

🗑️ pretty-format (removed)

🗑️ react-is (removed)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)