Skip to content

Fix React Server Components CVE vulnerabilities #98

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ethanniser merged 1 commit into from
Dec 12, 2025
Merged

Fix React Server Components CVE vulnerabilities #98

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@
"jose": "^5.9.4",
"linkedom": "^0.18.5",
"lucide-react": "^0.453.0",
"next": "15.0.6",
"next": "15.0.7",
Copy link

@cursor cursor bot Dec 12, 2025

Choose a reason for hiding this comment

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

Bug: Security fix claims to update React but doesn't

The PR description states it "updates your React, Next.js, and related Server Components packages" to fix CVE-2025-55182 (React2Shell) and related vulnerabilities. However, only next is updated from 15.0.6 to 15.0.7. The react and react-dom packages remain at the old release candidate version 19.0.0-rc-cd22717c-20241013 from October 2024. If React Server Components vulnerabilities require patched React packages as well, this fix may be incomplete and leave the application vulnerable.

Additional Locations (1)

Fix in Cursor Fix in Web

"openai": "^4.68.0",
"react": "19.0.0-rc-cd22717c-20241013",
"react-dom": "19.0.0-rc-cd22717c-20241013",
Expand Down
36 changes: 18 additions & 18 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading