Skip to content

🚨 [security] [web] Update all of nextjs 16.2.6 → 16.4.0 (minor) - #131

Open
depfu[bot] wants to merge 1 commit into
masterfrom
depfu/update/web/npm/group/nextjs-16.4.0
Open

🚨 [security] [web] Update all of nextjs 16.2.6 → 16.4.0 (minor)#131
depfu[bot] wants to merge 1 commit into
masterfrom
depfu/update/web/npm/group/nextjs-16.4.0

Conversation

@depfu

@depfu depfu Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint-config-next (16.2.6 → 16.4.0)

Sorry, we couldn't find anything useful about this release.

✳️ next (16.2.6 → 16.4.0) · Repo

Security Advisories 🚨

🚨 Next.js has information disclosure in development server's Model Context Protocol endpoint

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 with next dev are affected. Production deployments do not serve this endpoint.

🚨 Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages

Pending use cache fills 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:

  • A regular request that overlaps an editor's Draft Mode request receives unpublished content, without any authentication.
  • A Draft Mode request that overlaps a regular request receives published content instead of the draft.

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.

🚨 Next.js has cache poisoning of SSG and ISR pages in self-hosted applications

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.

🚨 Next.js has Server-Side Request Forgery in Image Optimization

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 no images.remotePatterns are configured, your app is not affected.

🚨 Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass

In Next.js App Router applications built with webpack, metadata image routes such as opengraph-image and twitter-image ignore the dynamicParams route segment option. An attacker can request metadata image URLs for dynamic segments that were deliberately excluded from generateStaticParams().

🚨 Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service

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.

🚨 Next.js: Remote Code Execution in next/og ImageResponse

Impact

The Node.js ImageResponse implementation from next/og is 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:

import { ImageResponse } from 'next/og'

export async function GET(request: Request) {

const value = new URL(request.url).searchParams.get('value') ?? ''


return new ImageResponse(

<svg width="1200" height="630">

<title>{value}</title>

</svg>

)

}

Applications using the Edge ImageResponse implementation, 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 ImageResponse implementation from next/og.

🚨 Next.js: Unauthenticated Remote Code Execution on windows-hosted servers

Impact

A vulnerability in applications using Pages and App router without Cache Component can lead to remote code execution when the server is hosted on machines using a Windows filesystem.

Workaround

There is no known workaround for affected windows-hosted applications. You should upgrade immediately if your server is hosted on Windows.

🚨 Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used

A vulnerability in the underlying libheif library used by sharp which Next.js uses for image optimization can lead to remote code execution when AVIF files are optimized.

Until a fix has propagated, optimization of AVIF files is disabled.

🚨 Next.js: Denial of Service in App Router using Server Actions

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.

🚨 Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale

Impact

Crafted requests targeting Next.js applications using App Router built with Turbopack and a single entry in config.i18n.locales can bypass middleware/proxy based authentication.

Workarounds

If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.

🚨 Next.js: Cache confusion of response bodies for requests with bodies

Impact

A server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped.

This only applies to fetch calls with a request that has a different init than the one passed to fetch.
Safe: fetch(new Request(init), init)
Unsafe: fetch(new Request(init), aDifferentInit)

Workarounds

No workaround exists besides upgrading. Applications using Pages Router are not vulnerable.

🚨 Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences

Impact

A server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped.

This is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache.

Workarounds

If you cannot upgrade, consider only making fetch requests with UTF-8 bodies (default in Next.js). Applications using Pages Router are not vulnerable.

🚨 Next.js: Unbounded Server Action payload in Edge runtime

Impact

Requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive memory consumption if that Server Actions uses the Edge runtime

Workarounds

If you cannot upgrade, ensure your hosting provider limits the request's body size. 5 MiB should be allowed at max by your hosting provider.

🚨 Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

Impact

A rewrites() or redirects() rule that builds its external destination hostname from request-controlled input can be pointed at an arbitrary hostname, regardless of the rule's hostname suffix. For a rewrite, Next.js proxies the request to that arbitrary host and serves the response from the application's origin, leading to Server-Side Request forgery. A redirects() rule configured this way is vulnerable to an Open Redirect.

This affects any destination that puts a dynamic segment in the hostname, whether from the path:

// next.config.js
module.exports = {
  async rewrites() {
    return [
      {
        source: '/:tenant',
        destination: 'https://:tenant.api.example.com',
      },
    ]
  },
}

or from a has capture:

// next.config.js
module.exports = {
  async rewrites() {
    return [
      {
        source: '/',
        has: [{ type: 'query', key: 'region', value: '(?<region>.+)' }],
        destination: 'https://:region.api.example.com',
      },
    ]
  },
}

Workarounds

If you cannot upgrade immediately, do not build the hostname of an external rewrites() or redirects() destination from user-controlled input. If a dynamic subdomain is required, constrain the value to hostname-safe characters: value: '(?<region>[a-z0-9-]+)'.

🚨 Next.js: Denial of Service in the Image Optimization API using SVGs

Impact

When self-hosting Next.js with the default image loader, the Image Optimization API can optimize remotely hosted images if configured (not enabled by default). If those images contain malicious content, they can cause CPU exhaustion in /_next/image endpoints.

  • If you are using config.images.remotePatterns, only the patterns in that array are impacted.
  • If you are using config.images.unoptimized: true, you are NOT impacted.
  • If you are using config.images.loader: 'custom', you are NOT impacted.
  • If you are using Vercel, you are NOT impacted.

Workarounds

If you cannot upgrade immediately, you can avoid the expensive work by setting config.experimental.imgOptSkipMetadata : true.

🚨 Next.js: Unauthenticated disclosure of internal Server Function endpoints

Impact

In Next.js applications using App Router, Server Actions (use server) or use cache endpoints can be disclosed bypassing any authentication on the pages where these endpoints are usually used.

Server Action IDs can be disclosed to unauthenticated users via publicly served client artifacts (for example, static chunks containing action references).

Affected users are applications using App Router + Server Actions.

By itself, this disclosure is typically a recon/enumeration primitive; however, it can increase risk when combined with other weaknesses.

Workarounds

Never assume any authentication claims at the use cache or use server boundary. Always authenticate within the boundary.

🚨 Next.js: Server-Side Request Forgery in Server Actions on custom servers

Impact

When a Server Action forwards or redirects a request, an attacker can cause the server to send that outbound request to a malicious host (Server-Side Request Forgery). This requires the attacker's request to control Host-associated headers. In some configurations, it's also possible to obtain internal values that weaken middleware/proxy authorization.

Applications that use Server Actions are affected when the incoming host header is not fixed to a trusted value. This typically occurs on custom servers, or on deployments not behind a proxy that pins the host. Managed hosting pins the host upstream and is not affected; next start and standalone output do the same from version 14.2 onward.

Workarounds

If you cannot upgrade, ensure clients do not control the host header your application receives. Pin or validate Host and X-Forwarded-Host at your edge or proxy. On version 14.2.0 and later, you can additionally set the __NEXT_PRIVATE_ORIGIN environment variable to your deployment's real origin:

__NEXT_PRIVATE_ORIGIN=https://www.example.com node server.js
Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-darwin-arm64 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-darwin-x64 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-darwin-arm64 (indirect, 1.2.4 → 1.3.4) · Repo

Release Notes

1.3.4

More info than we can show here.

1.3.3

More info than we can show here.

1.3.2

More info than we can show here.

1.3.1

More info than we can show here.

1.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-darwin-x64 (indirect, 1.2.4 → 1.3.4) · Repo

Release Notes

1.3.4

More info than we can show here.

1.3.3

More info than we can show here.

1.3.2

More info than we can show here.

1.3.1

More info than we can show here.

1.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-linux-arm (indirect, 1.2.4 → 1.3.4) · Repo

Release Notes

1.3.4

More info than we can show here.

1.3.3

More info than we can show here.

1.3.2

More info than we can show here.

1.3.1

More info than we can show here.

1.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-linux-arm64 (indirect, 1.2.4 → 1.3.4) · Repo

Release Notes

1.3.4

More info than we can show here.

1.3.3

More info than we can show here.

1.3.2

More info than we can show here.

1.3.1

More info than we can show here.

1.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-linux-s390x (indirect, 1.2.4 → 1.3.4) · Repo

Release Notes

1.3.4

More info than we can show here.

1.3.3

More info than we can show here.

1.3.2

More info than we can show here.

1.3.1

More info than we can show here.

1.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-linux-x64 (indirect, 1.2.4 → 1.3.4) · Repo

Release Notes

1.3.4

More info than we can show here.

1.3.3

More info than we can show here.

1.3.2

More info than we can show here.

1.3.1

More info than we can show here.

1.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-linuxmusl-arm64 (indirect, 1.2.4 → 1.3.4) · Repo

Release Notes

1.3.4

More info than we can show here.

1.3.3

More info than we can show here.

1.3.2

More info than we can show here.

1.3.1

More info than we can show here.

1.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-libvips-linuxmusl-x64 (indirect, 1.2.4 → 1.3.4) · Repo

Release Notes

1.3.4

More info than we can show here.

1.3.3

More info than we can show here.

1.3.2

More info than we can show here.

1.3.1

More info than we can show here.

1.3.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linux-arm (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linux-arm64 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linux-s390x (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linux-x64 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linuxmusl-arm64 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-linuxmusl-x64 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-wasm32 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-win32-ia32 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​img/sharp-win32-x64 (indirect, 0.34.5 → 0.35.5) · Repo

Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​next/env (indirect, 16.2.6 → 16.4.0) · Repo

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​next/eslint-plugin-next (indirect, 16.2.6 → 16.4.0)

Sorry, we couldn't find anything useful about this release.

↗️ @​swc/helpers (indirect, 0.5.15 → 0.5.23) · Repo · Changelog

↗️ fastq (indirect, 1.20.1 → 1.20.3) · Repo

Release Notes

1.20.3

More info than we can show here.

1.20.2

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ sharp (indirect, 0.34.5 → 0.35.5) · Repo

Security Advisories 🚨

🚨 sharp : Vulnerability in librsvg dependency CVE-2026-96889

Impact

A memory-related vulnerability has been discovered and fixed in the upstream librsvg dependency. When certain runtime-specific conditions apply, this vulnerability can lead to possible remote code execution (RCE) on glibc-based Linux.

Patches

Using prebuilt binaries provided by sharp?

Most people rely on the prebuilt binaries provided by sharp.

Please upgrade sharp to the latest version, currently 0.35.5, which provides librsvg 2.63.2.

Using a globally-installed librsvg?

Please ensure you are using the latest librsvg 2.63.2.

Workarounds

Add the following to your code to prevent sharp from decoding SVG images.

sharp.block({ operation: ["VipsForeignLoadSvg"] });

To avoid RCE, ensure you are using a node executable binary compiled as a Position Independent Executable (PIE). Most Linux package managers already use this security-hardening feature however be warned that the "official" Node.js binaries do not.
1

🚨 sharp: Vulnerabilities in libheif: GHSA-g89c-p67h-r497 and GHSA-2jg2-4ch7-h545

Impact

A number of vulnerabilities, two rated as "Critical" severity using CVSSv3, have been discovered and fixed in the upstream libheif dependency. These can lead to possible remote code execution (RCE) on glibc-based Linux when run under certain conditions.

The attack vector for these claims to be "network" however sharp does not provide any networking features so this vulnerability is down-rated to a "High" severity using CVSSv4 but please note its Subsequent System Impact.

Those processing untrusted input with versions of sharp prior to 0.35.4 are affected.

Patches

Using prebuilt binaries provided by sharp?

Most people rely on the prebuilt binaries provided by sharp.

Please upgrade sharp to the latest version, currently 0.35.4, which provides libheif 1.23.2.

Using a globally-installed libheif?

Please ensure you are using the latest libheif 1.23.2.

Workarounds

Add the following to your code to prevent sharp from decoding AVIF images.

sharp.block({ operation: ["VipsForeignLoadHeif"] });

Ensure you are using a node executable binary compiled as a Position Independent Executable (PIE). Most Linux package managers already do this for protection against RCE however be warned that the "official" Node.js binaries do not.

References

🚨 sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591

Impact

A number of vulnerabilities, two rated as "High" severity using CVSSv4, have been discovered and fixed in the upstream libvips dependency.

Those processing untrusted input with versions of sharp prior to 0.35.0 are affected.

Patches

Using prebuilt binaries provided by sharp?

Most people rely on the prebuilt binaries provided by sharp.

Please upgrade sharp to the latest version, currently 0.35.3, which provides libvips 8.18.3.

Using a globally-installed libvips?

Please ensure you are using the latest libvips 8.18.3.

Workarounds

Add the following to your code to prevent sharp from decoding GIF, TIFF and VIPS images.

sharp.block({ operation: ["VipsForeignLoadNsgif", "VipsForeignLoadTiff", "VipsForeignLoadVips"] });
Release Notes

0.35.5

More info than we can show here.

0.35.4

More info than we can show here.

0.35.3

More info than we can show here.

0.35.2

More info than we can show here.

0.35.1

More info than we can show here.

0.35.0

More info than we can show here.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 @​img/sharp-freebsd-wasm32 (added, 0.35.5)

🆕 @​img/sharp-webcontainers-wasm32 (added, 0.35.5)

🆕 @​emnapi/runtime (added, 1.11.3)

🆕 semver (added, 7.8.5)

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu Bot added the depfu label Oct 7, 2026
@depfu depfu Bot mentioned this pull request Oct 7, 2026
Closed

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants