fix(deps): bump next to 16.2.11 for the security release - #221
Merged
Conversation
Closes nine open advisories, including SSRF in rewrites and in Server Actions, the middleware/proxy bypass in App Router apps, unauthenticated disclosure of internal Server Function endpoints, cache confusion for requests with bodies, and several DoS paths. Done as a targeted bump rather than through the Dependabot PR: that PR's lockfile regeneration also pulled @emnapi/runtime 1.11.3, published today, which the minimumReleaseAge policy rejects until tomorrow morning. @emnapi/runtime comes from @img/sharp-wasm32 and has nothing to do with next, so bumping next alone keeps it at 1.11.2 and lets the security fix land now. The lockfile diff is next plus its swc binaries; postcss stays at 8.5.19.
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.
Closes the nine open
nextadvisories: SSRF in rewrites and in Server Actions, the middleware/proxy bypass in App Router apps, unauthenticated disclosure of internal Server Function endpoints, cache confusion for requests with bodies, unbounded Server Action payloads on Edge, and DoS in the Image Optimization API and App Router Server Actions.Replaces #218 rather than waiting on it. That PR's lockfile regeneration incidentally pulled
@emnapi/runtime1.11.3, published today, so theminimumReleaseAgepolicy rejects it until tomorrow morning.@emnapi/runtimecomes from@img/sharp-wasm32(sharp's wasm fallback) and has nothing to do with next, so a targeted bump keeps it at 1.11.2 and lets the security fix land today.next16.2.11 was published on 2026-07-21, so it clears the 24h policy. The lockfile diff isnextplus its@next/swc-*binaries and@next/env;postcssstays at 8.5.19.The proxy bypass one (GHSA for
>= 16.0.0, < 16.2.11) is the most relevant to us, sinceproxy.tsis what sets the nonce-based CSP and the security headers.#218 can be closed once this lands.