Repository navigation
fix(deps): update dependency next to v16.4.5 [security] - #149
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
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 15, 2026 03:38
2bfc83d to
005c0a5
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 27, 2026 18:23
005c0a5 to
a914404
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
November 11, 2026 20:59
2b5b313 to
e027231
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
November 16, 2026 19:03
e027231 to
0f83820
Compare
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
16.3.3→16.4.5Next.js: Remote Code Execution in next/og ImageResponse
GHSA-vcvr-r3jv-pc5j
More information
Details
Impact
The Node.js
ImageResponseimplementation fromnext/ogis affected by an upstream vulnerability. This can lead to remote code execution.Affected applications pass attacker-controlled values into SVG content, attributes, or styles during image generation:
Applications using the Edge
ImageResponseimplementation, or applications that do not pass attacker-controlled values into SVG content, attributes, or styles, are not affected.Workaround
If upgrading is not immediately possible, do not pass attacker-controlled values into SVG content, attributes, or styles rendered by the Node.js
ImageResponseimplementation fromnext/og.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js: Pending
use cachefill can leak Draft Mode content into regular responses and persisted pagesCVE-2026-94544 / GHSA-3w37-wq28-93x7
More information
Details
Pending
use cachefills are shared across requests for the same key without distinguishing Draft Mode requests from regular requests. When two such requests overlap, the second request receives the first request's fill:If the overlapping regular request prerenders a page — for example an on-demand prerender of a route that was not prerendered at build time — the unpublished content can be persisted into the generated page and served to all later visitors of that route until the page is revalidated. Since cached functions can be shared across routes, the poisoned page does not need to be the page the editor is previewing.
Sites are affected if they enable Cache Components (or
experimental.useCache) and serve Draft Mode previews whose cached functions return draft-dependent content.Severity
CVSS:4.0/AV:N/AC:H/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 has Server-Side Request Forgery in Image Optimization
CVE-2026-94483 / GHSA-cjq9-62q9-8jv4
More information
Details
Impact
An attacker-controlled, allow-listed remote URL can lead to server-side request forgery (e.g. to private IPs) during Image Optimization.
Workaround
Audit allow-listed remote URLs in
images.remotePatterns(see https://nextjs.org/docs/app/getting-started/images#remote-images) for hosts that may not be trusted with their DNS entries. If noimages.remotePatternsare configured, your app is not affected.Severity
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/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 has cache poisoning of SSG and ISR pages in self-hosted applications
CVE-2026-94543 / GHSA-4jqv-mc3x-m676
More information
Details
Self-hosted Next.js applications that use the Pages Router with statically generated (SSG) or incrementally regenerated (ISR) pages can have a page's cache entry replaced with content from a different route, causing the affected page to serve wrong content to every visitor until the entry is revalidated. Applications deployed on Vercel are not affected.
Severity
CVSS:4.0/AV:N/AC:H/AT:P/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 has information disclosure in development server's Model Context Protocol endpoint
CVE-2026-94486 / GHSA-39w2-rjm5-chcv
More information
Details
The Next.js development server (
next dev) exposes a Model Context Protocol endpoint that does not verify which website a request originates from, allowing a malicious website visited by the developer to read sensitive development data — including the project's location on disk, source code snippets from error reports, the route inventory, and development logs. Only applications run withnext devare affected. Production deployments do not serve this endpoint.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/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 has information disclosure in App Router metadata image routes via dynamicParams bypass
CVE-2026-94485 / GHSA-f87g-xv8r-7p7x
More information
Details
In Next.js App Router applications built with webpack, metadata image routes such as opengraph-image and twitter-image ignore the
dynamicParamsroute segment option. An attacker can request metadata image URLs for dynamic segments that were deliberately excluded fromgenerateStaticParams().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
CVE-2026-103004 / GHSA-h694-7cp9-m8p3
More information
Details
Impact
With Cache Components enabled (
cacheComponents: true), a'use cache'function that calls another'use cache'function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing 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 — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further.What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first.
Workarounds
There are no known workarounds. 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: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: Denial of Service in App Router using Server Actions
CVE-2026-94482 / GHSA-p3m5-59mp-jv5r
More information
Details
Impact
Crafted requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive CPU usage blocking processing of further requests in the same process.
Workarounds
No workaround exists besides upgrading. Applications using Pages Router or not using Server Actions are not vulnerable.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js: Unauthenticated Remote Code Execution in
use cachefunctions returning typed arraysGHSA-673q-mjm6-r5xr
More information
Details
Impact
A vulnerability in applications using App router with Cache Component can lead to remote code execution. The application needs to have a
use cachefunction that returns multiple typed arrays.Workaround
There is no known workaround for affected applications with such
use cachefunctions. You should upgrade immediately even if your application does not have similar functions.Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.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: 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: 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: 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-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
v16.4.1Compare Source
This release contains security fixes for the following advisories:
Critical:
use cachefunctions returning typed arraysHigh:
v16.4.0Compare Source
Check out the 16.4 announcement post to get an overview of the changes.
Core Changes
falsevalues forresolveAliasconfig: #93331Misc Changes
exports: #96381exportsafter amodule.exports = {}writes: #96380cbb046ab-20260731to7dfc7ccd-20260803: #965507dfc7ccd-20260803to11eddecd-20260805: #96735loadManifestto return undefined withhandleMissing: #96530nextjs-bot: #96683config.experimental.appNewScrollHandler: #95602type: 'text'in rules, and error on binding imports of non-ESM modules: #96558Configuration
📅 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.