fix: upgrade Next.js to 15.5.18 for security vulnerabilities#17676
Open
fix: upgrade Next.js to 15.5.18 for security vulnerabilities#17676
Conversation
Addresses 13 CVEs disclosed 2026-05-06 including: - GHSA-26hh-7cqf-hhc6 (High): Middleware bypass via segment-prefetch - GHSA-492v-c6pp-mqqv (High): Middleware bypass via dynamic route injection - GHSA-c4j6-fc7j-m34r (High): SSRF via WebSocket upgrades - GHSA-8h8q-6873-q5fj (High): DoS with Server Components - GHSA-mg66-mrh9-m8jx (High): DoS via Cache Components - CVE-2026-23870 (High): React Server Components DoS See: https://developers.cloudflare.com/changelog/post/2026-05-06-react-nextjs-vulnerabilities/ Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
DESCRIBE YOUR PR
Upgrades Next.js from
^15.5.14to^15.5.18to address 13 critical and high-severity CVEs disclosed on 2026-05-06.Key vulnerabilities addressed:
x-nextjs-data/__nextjs_segment_prefetchheaders — the follow-up fix requiring 15.5.18next devReferences:
Changes:
package.json: bumpednextfrom^15.5.14to^15.5.18pnpm-lock.yaml: updated lockfile accordinglyIS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: