Skip to content

[Snyk] Security upgrade react-scripts from 3.4.1 to 5.0.0#244

Open
xtremebeing wants to merge 1 commit intodevelopmentfrom
snyk-fix-95c983dcc592f71642f1be5927d64c0f
Open

[Snyk] Security upgrade react-scripts from 3.4.1 to 5.0.0#244
xtremebeing wants to merge 1 commit intodevelopmentfrom
snyk-fix-95c983dcc592f71642f1be5927d64c0f

Conversation

@xtremebeing
Copy link

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Use of a Cryptographic Primitive with a Risky Implementation
SNYK-JS-ELLIPTIC-14908844
  708  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Copilot AI review requested due to automatic review settings January 19, 2026 22:36
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR upgrades react-scripts from version 3.4.1 to 5.0.0 to address a cryptographic vulnerability (SNYK-JS-ELLIPTIC-14908844) with a severity score of 708. However, this is a major version upgrade that introduces breaking changes requiring additional dependency updates.

Changes:

  • Upgraded react-scripts from 3.4.1 to 5.0.0 to fix security vulnerability in the elliptic cryptographic library

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

"react-paginate": "^6.3.2",
"react-router-dom": "^5.2.0",
"react-scripts": "3.4.1",
"react-scripts": "5.0.0",
Copy link

Copilot AI Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upgrading react-scripts to 5.0.0 requires React 17 or higher, but the current project uses React 16.13.1 (line 12). This version mismatch will cause the application to fail. You need to upgrade react and react-dom to at least version 17.0.0 or 18.0.0 to be compatible with react-scripts 5.0.0.

Copilot uses AI. Check for mistakes.
"react-paginate": "^6.3.2",
"react-router-dom": "^5.2.0",
"react-scripts": "3.4.1",
"react-scripts": "5.0.0",
Copy link

Copilot AI Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upgrading react-scripts to 5.0.0 is incompatible with the current React version 16.13.1 specified in this package.json. React-scripts 5.0.0 requires React 17 or higher. This upgrade will cause the application and tests to fail. You must also upgrade react and react-dom to at least version 17.0.0, along with updating @testing-library/react and other testing dependencies to compatible versions.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments