Fix React Server Components CVE vulnerabilities

[vercel]

Important

This is an automatic PR generated by Vercel to help you with patching efforts. We can't guarantee it's comprehensive, and it may contain mistakes. Please review our guidance before merging these changes.

A critical remote code execution (RCE) vulnerability in React Server Components, impacting frameworks such as Next.js, was identified in the project whale-manager. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.

This issue is tracked under:

• GitHub Security Advisory: GHSA-9qr9-h5gf-34mp
• React Advisory: CVE-2025-55182
• Next.js Advisory: CVE-2025-66478

This automated pull request upgrades the affected React and Next.js packages to patched versions that fully remediate the issue.

More Info | security@vercel.com

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
whale-manager	Error		Feb 12, 2026 6:39pm

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​radix-ui/​react-label@​2.1.7 ⏵ 2.1.8
	@​radix-ui/​react-separator@​1.1.7 ⏵ 1.1.8
	next@​15.4.6 ⏵ 15.4.10	+6	+57	+1	+47
	@​radix-ui/​react-slot@​1.2.4
	@​radix-ui/​react-switch@​1.2.5 ⏵ 1.2.6
	@​radix-ui/​react-tabs@​1.1.12 ⏵ 1.1.13
	@​radix-ui/​react-toast@​1.2.14 ⏵ 1.2.15
	@​types/​pg@​8.15.5 ⏵ 8.16.0	+1		+1
	expo-sqlite@​15.2.14 ⏵ 16.0.10	+1		+1	+1
	@​op-engineering/​op-sqlite@​14.1.4 ⏵ 15.2.5	+2		+1	-1
	bun-types@​1.2.20 ⏵ 1.3.9	+1		+1		-30
	@​libsql/​client-wasm@​0.15.10 ⏵ 0.17.0	-1		+1	-1
	bcryptjs@​3.0.2 ⏵ 3.0.3	+1
	postgres@​3.4.7 ⏵ 3.4.8	+1
	@​prisma/​client@​6.13.0 ⏵ 7.4.0	+12		+1
	bufferutil@​4.0.9 ⏵ 4.1.0	+1
	@​neondatabase/​serverless@​1.0.1 ⏵ 1.0.2
	express-session@​1.18.2 ⏵ 1.19.0	+1		+1
	express@​5.1.0 ⏵ 5.2.1
	@​tanstack/​react-query@​5.84.2 ⏵ 5.90.21			+1	+1
	cors@​2.8.5 ⏵ 2.8.6
	ws@​8.18.3 ⏵ 8.19.0	-1
	drizzle-orm@​0.44.4 ⏵ 0.45.1			+1
	gel@​2.1.1 ⏵ 2.2.0				-5
	better-sqlite3@​12.2.0 ⏵ 12.6.2
	@​libsql/​client@​0.15.10 ⏵ 0.17.0			+1
	kysely@​0.28.5 ⏵ 0.28.11			+1	+3
	pg@​8.16.3 ⏵ 8.18.0	+1		+1
	@​electric-sql/​pglite@​0.3.7 ⏵ 0.3.15
	mysql2@​3.14.3 ⏵ 3.17.0				-2
	@​slack/​web-api@​7.9.3 ⏵ 7.14.0				+3
	axios@​1.11.0 ⏵ 1.13.5	-1	+22
See 4 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		License policy violation: npm bcryptjs under BSD-3-Clause-HP License: BSD-3-Clause-HP - the applicable license policy does not allow this license (4) (package/LICENSE) From: package.json → npm/bcryptjs@3.0.3 ℹ Read more on: This package | This alert | What is a license policy violation? 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: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/bcryptjs@3.0.3. 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