Repository navigation
fix(deps): update dependency next to v16.4.5 [security] - #552
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
This branch has not been deployed
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.
This PR contains the following updates:
16.4.1→16.4.5Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
CVE-2026-119790 / GHSA-mfr8-8qww-v76h
More information
Details
Next.js applications with
'use cache'can disclose cached data across root params when the same'use cache'function is called both directly during rendering and throughunstable_cache(), and that function reads a root param. Root params are route parameters of the root layout, and applications commonly use them to scope data, for example per locale.During a cold process start, a cross-request deduplication race allowed an
unstable_cache()call to join the in-flight fill of a concurrent direct call and receive its result, bypassing the root param check that would normally reject it.unstable_cache()then stored that result under a cache key without root params, so subsequent requests for other root param values received the same entry until it is revalidated or evicted. Cached data produced for one root param value is returned to requests for other values.Exploitation requires the
unstable_cache()request to arrive while the function's first fill after a process start is still in flight. Outside this race, the nesting already throws an error:'use cache' inside unstable_cache() is unsupported, and avoiding it is a complete workaround.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
CVE-2026-119351 / GHSA-vc7v-qv4w-wrv8
More information
Details
With Cache Components enabled, an outer
'use cache'function can be keyed incorrectly even when its inner'use cache'call generates a fresh entry. If the inner function reads a root param (vianext/root-params) and returns a value that still contains pending promises — for example an object with data that is ready immediately alongside slower data — React Flight delivers the ready portion to the outer function before the inner entry has finished publishing its root param dependencies. The outer function can then finish, and its cache entry is persisted under a key that omits that root param. The entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value. Entries written this way can also ignore tag invalidation and cache lifetimes of the nested caches they consumed.What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first.
This is a variant of GHSA-h694-7cp9-m8p3 that the fix for that advisory does not cover: it does not require the inner call to be served from an existing entry, and it does not depend on a slow cache handler.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
CVE-2026-119350 / GHSA-vvgp-ww4w-46vf
More information
Details
Self-hosted Next.js applications served with
next startand built withcacheComponents: truebut without Partial Prefetching accept a request-supplied route param value as a prerender placeholder. One unauthenticated GET request can poison the fallback shell cache entry that a family of routes shares.Such a route is served from a shell that keeps its never-prerenderable params as placeholders, so every value of those params shares one cache entry. A path segment equal to the percent-encoded, bracketed name of its own route param is treated as an unresolved placeholder, and only that param is deferred. A layout above it then renders its concrete value into the shell during the blocking render, and the result, including its HTTP status, is stored under the shared key.
Depending on the application, the stored entry is one of the following:
notFound(): served to every URL under the shell key with"revalidate": false, across server restarts, with no error logged.Preconditions
cacheComponents: truewithpartialPrefetchingunset orfalse.next start.generateStaticParams) whose requested value was not generated at build time.Workarounds
Set
partialPrefetching: trueinnext.config. Otherwise, apps should upgrade to the patched version as soon as possible.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
CVE-2026-119346 / GHSA-f3mh-rxg3-f5g2
More information
Details
Next.js applications that set cookies through
NextResponseon Edge runtime routes — App Router route handlers and Pages Router Edge API routes — send an internalx-middleware-set-cookieheader in the public response, duplicating the cookie value and its attributes. This makes HttpOnly cookies, such as session tokens, readable by JavaScript running on the same origin when an application sets a sensitive cookie on an affected response.Severity
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js: SVG rejection bypass in the image optimization
CVE-2026-119347 / GHSA-7qx7-33qx-rqx2
More information
Details
On self-hosted deployments, the Next.js image optimizer (
/_next/image) can be made to process an attacker-supplied SVG even when SVG support is disabled withdangerouslyAllowSVG: false(the default). This reaches an SVG parser the application intended to keep disabled, increasing exposure to denial of service and SVG decoder vulnerabilities.Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
CVE-2026-119348 / GHSA-pc58-hwjq-p385
More information
Details
Self-hosted Next.js applications (App Router route handlers and the fetch cache) that return a fetched upstream response unchanged can emit a response whose declared framing does not match the body actually sent. When such an application sits behind an HTTP/1.1 reverse proxy that permits pipelined response queueing, a crafted upstream response can desynchronize responses between clients, enabling response injection and disclosure of other clients' responses.
Severity
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
CVE-2026-119349 / GHSA-rhh4-g77r-r9qj
More information
Details
Next.js App Router applications that pass binary arguments (such as Uint8Array or Blob values) to functions using the
use cachedirective can produce identical cache keys for distinct arguments, allowing cached results to be shared across users — cross-user disclosure of cached data or cache poisoning. This affects applications usinguse cachewith binary arguments.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
vercel/next.js (next)
v16.4.5Compare Source
This release contains security fixes for the following advisories:
Moderate
v16.4.4Compare Source
Core Changes
reads fallback params after a client navigationdeployment test (#100668)Credits
Huge thanks to @icyJoseph, @mischnic, @wbinnssmith, @lukesandberg, and @eps1lon for helping!
v16.4.3Compare Source
Core Changes
Credits
Huge thanks to @mischnic, @lukesandberg, @acdlite, @eps1lon, and @sokra for helping!
v16.4.2Compare Source
What's Changed
Full Changelog: vercel/next.js@v16.4.1...v16.4.2
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.