Skip to content

[Snyk] Fix for 3 vulnerabilities#210

Open
naiba4 wants to merge 2 commits intodevfrom
snyk-fix-057371eed237c245b94a10f8006c6577
Open

[Snyk] Fix for 3 vulnerabilities#210
naiba4 wants to merge 2 commits intodevfrom
snyk-fix-057371eed237c245b94a10f8006c6577

Conversation

@naiba4
Copy link
Owner

@naiba4 naiba4 commented Jan 29, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json

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.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
  696  
medium severity Directory Traversal
SNYK-JS-TAR-15032660
  693  
medium severity Directory Traversal
SNYK-JS-TAR-15127355
  596  

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Directory Traversal

@changeset-bot
Copy link

changeset-bot bot commented Jan 29, 2026

⚠️ No Changeset found

Latest commit: 1d498ae

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security
Copy link

socket-security bot commented Jan 29, 2026

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Medium
Network access: npm web3 in module globalThis["fetch"]

Module: globalThis["fetch"]

Location: Package overview

From: ?npm/web3@4.0.1

ℹ Read more on: This package | This alert | What is network access?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/web3@4.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
Embedded URLs or IPs: npm react-scripts

URLs: 0.0.0.0, https://cra.link/advanced-config, https://facebook.github.io/create-react-app/docs/updating-to-new-releases, https://cra.link/templates, README.md, README.old.md, https://reactjs.org/blog/2018/10/01/create-react-app-v2.html, http://goo.gl/forms/Bi6CZjk1EqsdelXk1, https://github.com/facebook/create-react-app/issues/293, https://github.com/facebook/create-react-app/issues/1065, https://github.com/facebook/create-react-app/issues/387.

Location: Package overview

From: ?npm/react-scripts@5.0.1

ℹ Read more on: This package | This alert | What are URL strings?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-scripts@5.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Block Low
Embedded URLs or IPs: npm web3

URLs: ws://some.local-or-remote.node:8546, https://www.alchemyapi.io/supernode, https://eth-mainnet.alchemyapi.io/v2/your-api-key, ws://remotenode.com:8546, https://links.ethers.org/v5-errors-, e.name:, https://github.com/goerli/testnet, https://goerli.etherscan.io/block/7382818, https://ethstats.net/, https://etherscan.io/block/15537393, https://github.com/ethereum/go-ethereum/pull/23730, https://sepolia.etherscan.io/block/1450408, https://eips.ethereum.org/EIPS/eip-1153, https://eips.ethereum.org/EIPS/eip-1559, https://eips.ethereum.org/EIPS/eip-2315, https://eips.ethereum.org/EIPS/eip-2537, https://eips.ethereum.org/EIPS/eip-2565, https://eips.ethereum.org/EIPS/eip-2718, https://eips.ethereum.org/EIPS/eip-2929, https://eips.ethereum.org/EIPS/eip-2930, https://eips.ethereum.org/EIPS/eip-3198, https://eips.ethereum.org/EIPS/eip-3529, https://eips.ethereum.org/EIPS/eip-3540, https://eips.ethereum.org/EIPS/eip-3541, https://eips.ethereum.org/EIPS/eip-3607, https://eips.ethereum.org/EIPS/eip-3651, https://eips.ethereum.org/EIPS/eip-3670, https://eips.ethereum.org/EIPS/eip-3675, https://eips.ethereum.org/EIPS/eip-3855, https://eips.ethereum.org/EIPS/eip-3860, https://eips.ethereum.org/EIPS/eip-4345, https://eips.ethereum.org/EIPS/eip-4399, https://eips.ethereum.org/EIPS/eip-5133, https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/arrow-glacier.md, https://eips.ethereum.org/EIPS/eip-2070, https://eips.ethereum.org/EIPS/eip-609, https://eips.ethereum.org/EIPS/eip-1013, https://eips.ethereum.org/EIPS/eip-779, https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/gray-glacier.md, https://eips.ethereum.org/EIPS/eip-606, https://eips.ethereum.org/EIPS/eip-1679, https://github.com/ethereum/eth1.0-specs/blob/master/network-upgrades/mainnet-upgrades/london.md, https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/merge.md, https://eips.ethereum.org/EIPS/eip-2384, https://eips.ethereum.org/EIPS/eip-1716, https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/shanghai.md, https://eips.ethereum.org/EIPS/eip-607, https://eips.ethereum.org/EIPS/eip-608, this._socketConnection.OPEN:return

Location: Package overview

From: ?npm/web3@4.0.1

ℹ Read more on: This package | This alert | What are URL strings?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/web3@4.0.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

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