fix(deps): update next 15.5.18 and react 19.0.6 [security]#1591
Merged
Conversation
Address the Next.js May 2026 coordinated security release (13 advisories including auth bypass, SSRF, cache poisoning, XSS, DoS). Bump: - next: 15.5.10 -> 15.5.18 - react: 19.0.0 -> 19.0.6 - react-dom: 19.0.0 -> 19.0.6 - eslint-config-next: 15.1.4 -> 15.5.18 (align with next) - @next/mdx: -> 15.5.18 (transitive realignment) - @next/third-parties: -> 15.5.18 (transitive realignment) Refs: https://vercel.com/changelog/next-js-may-2026-security-release
|
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.
Summary
Address the Next.js May 2026 coordinated security release (May 7, 2026) which fixes 13 advisories including:
Tracking tweet: https://x.com/nextjs/status/2052489312944759202
Changes
nextreactreact-domeslint-config-next@next/mdx@next/third-partiesStaying on the 15.x line per the advisory (15.5.18 and 16.2.6 are co-equal patched targets) to minimize risk.
Test plan
yarn installcleanyarn lint— no new errors (only pre-existing_error/unused-var warnings)npx tsc --noEmit— zero type errorsyarn build— verified via Vercel preview deploy (local build needsNEXT_PUBLIC_ECOSYSTEM_BASE_URIenv which isn't in my local; this is a pre-existing env issue, not a regression)🤖 Generated with Claude Code