Fix RSC vulnerabilities

[shahbaz17]

Fixes vulnerabilities identified in the React Server Components (RSC) protocol.

---

Note

Update Next.js versions in partners/dynamic, partners/web3auth, quickstarts/next, and quickstarts/wagmi with corresponding lockfile changes.

• Dependencies:
  • Bump next:
    • partners/dynamic/package.json: 15.3.6 → 15.3.8
    • partners/web3auth/package.json: 15.4.8 → 15.4.10
    • quickstarts/next/package.json: 15.5.7 → 15.5.9
    • quickstarts/wagmi/package.json: 15.4.8 → 15.4.10
  • Update corresponding pnpm-lock.yaml entries (including @next/env and next resolutions) in each project directory.

^{Written by Cursor Bugbot for commit d1a9e95. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
metamask-connectkit-demo	Ready	Preview	Comment	Dec 12, 2025 5:29am
metamask-dynamic-demo	Ready	Preview	Comment	Dec 12, 2025 5:29am
metamask-javascript-demo	Ready	Preview	Comment	Dec 12, 2025 5:29am
metamask-next-demo	Ready	Preview	Comment	Dec 12, 2025 5:29am
metamask-rainbowkit-demo	Ready	Preview	Comment	Dec 12, 2025 5:29am
metamask-react-demo	Ready	Preview	Comment	Dec 12, 2025 5:29am
metamask-sdk-examples	Ready	Preview	Comment	Dec 12, 2025 5:29am
metamask-wagmi-demo	Ready	Preview	Comment	Dec 12, 2025 5:29am
metamask-web3auth-demo	Ready	Preview	Comment	Dec 12, 2025 5:29am

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​15.4.8 ⏵ 15.3.8	+11	+14		+1
	next@​15.4.8 ⏵ 15.4.10	+11	+18	+1	+1
	next@​15.4.8 ⏵ 15.5.9	+18	+18	+10	+3	+31

View full report

[socket-security]

Warning

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Potential code anomaly (AI signal): npm next is 78.0% likely to have a medium risk anomaly Notes: The fragment represents a sophisticated Edge VM sandbox aimed at running untrusted code with controlled IO. While not overtly malicious, its capability to patch native constructors, generate and evaluate runtime code, and route network-like fetch events through sandboxed listeners creates meaningful security risks if misused or insufficiently isolated. This warrants thorough threat modeling, strict supply-chain controls, and explicit isolation guarantees in the hosting environment before deploying in production. Confidence: 0.78 Severity: 0.60 From: partners/dynamic/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Warn		Potential code anomaly (AI signal): npm next is 90.0% likely to have a medium risk anomaly Notes: The code appears to implement expected behavior for downloading and running mkcert to produce local development TLS certificates. It does not contain obvious malware (no credential exfiltration, no reverse shell code, no obfuscated payloads). However there are significant supply-chain and injection risks: it downloads an executable at runtime from a remote URL and executes it, and it interpolates an unescaped host value into a shell command passed to child_process.execSync, creating a command-injection vector if host is attacker-controlled. Recommendation: validate or sanitize 'host' input, avoid executing downloaded binaries without integrity checks (e.g., verify checksum/signature), and prefer execFile/spawn with argument arrays instead of string commands to avoid shell interpretation. Use stricter error handling to surface failures instead of silently falling back. Confidence: 0.90 Severity: 0.60 From: partners/dynamic/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Warn		Potential code anomaly (AI signal): npm next is 70.0% likely to have a medium risk anomaly Notes: Selected report 1 provides a thorough evaluation of decorator-related runtime utilities and concludes low risk with potential for finishers to alter constructors if used with untrusted inputs. The improved assessment confirms normal, expected behavior for Babel decorator infrastructure and notes that the primary risk lies in the finishers channel if untrusted code is supplied. Security risk remains low to moderate depending on input provenance; malware likelihood is negligible based on the fragment. Confidence: 0.70 Severity: 0.55 From: partners/dynamic/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Warn		Potential code anomaly (AI signal): npm next is 78.0% likely to have a medium risk anomaly Notes: The fragment represents a sophisticated Edge VM sandbox aimed at running untrusted code with controlled IO. While not overtly malicious, its capability to patch native constructors, generate and evaluate runtime code, and route network-like fetch events through sandboxed listeners creates meaningful security risks if misused or insufficiently isolated. This warrants thorough threat modeling, strict supply-chain controls, and explicit isolation guarantees in the hosting environment before deploying in production. Confidence: 0.78 Severity: 0.60 From: partners/web3auth/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Warn		Potential code anomaly (AI signal): npm next is 90.0% likely to have a medium risk anomaly Notes: The code appears to implement expected behavior for downloading and running mkcert to produce local development TLS certificates. It does not contain obvious malware (no credential exfiltration, no reverse shell code, no obfuscated payloads). However there are significant supply-chain and injection risks: it downloads an executable at runtime from a remote URL and executes it, and it interpolates an unescaped host value into a shell command passed to child_process.execSync, creating a command-injection vector if host is attacker-controlled. Recommendation: validate or sanitize 'host' input, avoid executing downloaded binaries without integrity checks (e.g., verify checksum/signature), and prefer execFile/spawn with argument arrays instead of string commands to avoid shell interpretation. Use stricter error handling to surface failures instead of silently falling back. Confidence: 0.90 Severity: 0.60 From: partners/web3auth/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.
Warn		Potential code anomaly (AI signal): npm next is 78.0% likely to have a medium risk anomaly Notes: The code is a legitimate worker orchestration utility for parallel build tasks, consistent with Next.js build tooling. The primary security concerns arise from reliance on private internals of an external library (fragility and potential breakage with library updates) and exposure of environment/config via forked processes (IS_NEXT_WORKER, NODE_OPTIONS). There is no evidence of malicious activity such as data theft or remote control in this fragment. Overall, it presents moderate security risk due to integration fragility and potential information leakage through logs, but not due to explicit malware. Confidence: 0.78 Severity: 0.60 From: partners/web3auth/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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