Repository navigation
chore(deps): update dependency next to v16.4.1 [security] - #703
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 22, 2026 18:11
e362c84 to
072e064
Compare
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
16.3.6→16.4.1Next.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 OSV and 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 OSV and 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 OSV and 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 OSV and 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 OSV and 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 OSV and the GitHub Advisory Database (CC-BY 4.0).
Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service
CVE-2026-94484 / GHSA-mcj8-r9mp-w47p
More information
Details
Next.js applications that use a root-level catch-all page together with statically generated or Incremental Static Regeneration routes can have their shared response cache poisoned by a single unauthenticated crafted request.
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 OSV and the GitHub Advisory Database (CC-BY 4.0).
Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used
GHSA-2464-fhr4-w9xw
More information
Details
Impact
A memory-related vulnerability has been discovered in an upstream library used for Image Optimization can lead to possible remote code execution (RCE) when Next.js runs on glibc-based Linux.
Workaround
Ensure the version of
sharpused by Next.js is greater than or equal to0.35.5. Fresh installs automatically get a fixed version ofsharp.Upgrading Next.js to the patched versions will ensure package managers automatically provide a fixed version of
sharpto Next.js.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 OSV and 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 OSV and 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 OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
vercel/next.js (next)
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: #96558turbopack/packagesand relocate devlow topackages/: #96860experimental.serverMinification& expandexperimental.turbopackMinify: #96578turbopackChunkingdocumentation page for pages router: #96698next buildinstead: #96746export const dynamic = 'force-static'to Route Handlers example on Static Exports: #96964encodeCacheTagtoencodeHeaderSafe: #96936'use cache'debug logs with the full directive: #97037ScrollAndMaybeFocusHandlertoScrollHandler: #96828var x = module.exports = {}: #97130use-cache-custom-handler-devtests: #97187clustersto chunking heuristics: #95157cache-components-dev-streamingassertions: #97246use-cache-default-profile-expire-zerotests: #97250nccbeforepnpm build: #9723411eddecd-20260805to22e4f993-20260811: #97249satoriand@vercel/og: #97276'use cache: private'in route handlers: #9734922e4f993-20260811toeb8feb71-20260814: #97382exports*unit fixtures: #97459nextversion to be available on npm before deploy tests: #97460unstable_eager: #97524eb8feb71-20260814toeafeac09-20260819: #97636prerender-native-modulesuite to local fixture packages: #97542turbopack-reportssqlite3dependency with a local addon fixture: #97541sqlite3build approval from thesharp-basicsuite: #97540import.meta.globvalues the ESM namespace: #96559Configuration
📅 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.