chore: upgrade next to ^16.2.11 to address CVE-2026-64647#1499
Draft
linear-code[bot] wants to merge 2 commits into
Draft
chore: upgrade next to ^16.2.11 to address CVE-2026-64647#1499linear-code[bot] wants to merge 2 commits into
linear-code[bot] wants to merge 2 commits into
Conversation
Co-authored-by: linear-code[bot] <222613912+linear-code[bot]@users.noreply.github.com>
Co-authored-by: linear-code[bot] <222613912+linear-code[bot]@users.noreply.github.com>
Contributor
License Audit❌ Audit failed to produce results. Check the workflow logs for details. |
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.
Fixes SOU-1576
Addresses CVE-2026-64647 (Next.js cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences), fixed in
next16.2.11.The top-level
nextdependency inpackages/webis^16.2.6, which already admits the patched 16.2.11, so refreshing the lockfile bumps it.@react-email/ui@6.1.4additionally pinsnextto an exact16.2.6, so a qualifiedresolutionsoverride (next@npm:16.2.6→^16.2.11) is added to move that instance too.yarn why next --recursivenow reports 16.2.11 for both.