Fix React Server Components RCE vulnerability#1
Draft
vercel[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
Updated dependencies to fix Next.js 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>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
vbh1v
pushed a commit
that referenced
this pull request
Apr 18, 2026
- Delete Section 2 ("A brand that ... rewards you while keeping Solana Strong") with navy vertical bar, orange underline, cyan highlighter on "Strong", and blue-glitter PNG — tonal collision with trustworthy+expert+direct voice and violates principles 1 and 5
- Replace three full-bleed stat monoliths (Established 2022 / Current Staked / APY) with one editorial stat strip: eyebrow label + four-column grid of tabular-nums numerals + provenance line linking to stakewiz
- Numbers render at text-5xl/6xl/7xl off-black on tinted off-white. Units (SOL, %) at smaller size in muted-foreground. Data wears a suit (principle 3)
- Expand validatorData state + fetch to include commission and uptime (stakewiz returns both)
- Provenance line folds "Established in 2022" into a single subordinate sentence instead of a full-viewport monument
- Reframe "The Team" header as editorial eyebrow + headline + lede; drop orange vertical bar (impeccable BAN #1 equivalent)
- Drop orange vertical bar in the Stake-in-30s wallet section
Net effect: four min-h-screen sections replaced with ~half a viewport. Page scroll shortens dramatically; signal density goes up.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
vbh1v
pushed a commit
that referenced
this pull request
Apr 18, 2026
…uote
Stakewiz status sentence:
- Replace the hacky .replace("stakewiz.com", "") hack with two typed lookup tables (status label + status sentence)
- Produces clean, grammatical prose across live / fallback / loading states instead of "Live data from , refreshed ..." with the stray comma
Blog blockquote:
- Strip border-l-4 border-brand-cyan (impeccable BAN #1 equivalent) from PortableTextComponents.tsx blockquote variant
- Replace with a leading ornate quotation mark in brand-orange, larger serif-style type treatment, no left stripe
- Uses Unicode U+201C via Tailwind before:content-[...]
Post-polish detector: 30 -> 0 anti-patterns across app/ + components/
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 v0-build-first-page. 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