Skip to content

Fix React Server Components CVE vulnerabilities#1

Closed
vercel[bot] wants to merge 1 commit intomainfrom
vercel/react-server-components-cve-vu-qhrwe3
Closed

Fix React Server Components CVE vulnerabilities#1
vercel[bot] wants to merge 1 commit intomainfrom
vercel/react-server-components-cve-vu-qhrwe3

Conversation

@vercel
Copy link
Copy Markdown

@vercel vercel Bot commented Jan 16, 2026

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 river-journal. The vulnerability enables unauthenticated RCE on the server via insecure deserialization in the React Flight protocol.

This issue is tracked under:

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

Updated dependencies to fix Next.js and React CVE vulnerabilities.

The fix-react2shell-next tool automatically updated the following packages to their secure versions:
- next
- react-server-dom-webpack
- react-server-dom-parcel  
- react-server-dom-turbopack

All package.json files have been scanned and vulnerable versions have been patched to the correct fixed versions based on the official React advisory.

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
@vercel
Copy link
Copy Markdown
Author

vercel Bot commented Jan 16, 2026

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

Project Deployment Review Updated (UTC)
river-journal Error Error Jan 16, 2026 6:21pm

@CharlesCoeder
Copy link
Copy Markdown
Owner

Next.js had an internal security vulnerability for a specific version, so Vercel was knocking on the door asking us to upgrade versions. closing because I upgraded myself. yay for first PR on the repo

CharlesCoeder added a commit that referenced this pull request May 6, 2026
…n replay

Lands the TanStack Query v5 layer alongside Legend-State for plaintext
server-visible data. Establishes the eager-import discipline so
setMutationDefaults registers at module load before
PersistQueryClientProvider mounts (the documented #1 footgun in the
two-state-libs architecture).

- packages/app/state/queryClient.ts + .native.ts: singleton client with
  retry/exponential backoff defaults, dehydrateOptions overriding
  shouldDehydrateMutation to persist post and report mutations even
  while in-flight, RN focusManager + onlineManager wiring
- packages/app/state/queryStorage.ts + .native.ts: AsyncStorage shim
  layered over the existing IndexedDB DB (DB_VERSION 5→6, new
  'tanstack-query' table) on web/desktop and a dedicated rj-tq MMKV
  on native; resilient try/catch with undefined fallback
- packages/app/state/collective/mutations.ts: TODO-marker stub for the
  upcoming mutation-defaults registration; sideEffects opt-out wired
- packages/app/provider/index.tsx: wraps ToastProvider in
  PersistQueryClientProvider with onSuccess=resumePausedMutations,
  24h maxAge, dev-only ReactQueryDevtools
- apps/{web,desktop,mobile}/app/{layout,_layout}.tsx: eager mutations
  import on line 1 to fix the registration-ordering footgun
- vitest stubs for @react-native-community/netinfo

Tests: 37 integration assertions across queryClient, boundary-rule,
and provider-wiring suites — all green.
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.

1 participant