Skip to content

fix(deps): update dependency next to v16.4.5 [security] - #149

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-next-vulnerability
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-next-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
next (source) 16.3.3 → 16.4.5 age confidence

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

GHSA-vcvr-r3jv-pc5j

More information

Details

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.

Severity

  • CVSS Score: 9.5 / 10 (Critical)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


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

CVE-2026-94544 / GHSA-3w37-wq28-93x7

More information

Details

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.

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

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

Severity

  • CVSS Score: 8.3 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

References

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 Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

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

Severity

  • CVSS Score: 2.3 / 10 (Low)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

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 dynamicParams route segment option. An attacker can request metadata image URLs for dynamic segments that were deliberately excluded from generateStaticParams().

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

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 Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

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 Score: 8.2 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Next.js: Unauthenticated Remote Code Execution in use cache functions returning typed arrays

GHSA-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 cache function that returns multiple typed arrays.

Workaround

There is no known workaround for affected applications with such use cache functions. You should upgrade immediately even if your application does not have similar functions.

Severity

  • CVSS Score: 9.5 / 10 (Critical)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N

References

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 through unstable_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 Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

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 (via next/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 Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

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 NextResponse on Edge runtime routes — App Router route handlers and Pages Router Edge API routes — send an internal x-middleware-set-cookie header 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 Score: 6.0 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

References

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 Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

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 with dangerouslyAllowSVG: 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 Score: 6.9 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

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 cache directive 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 using use cache with binary arguments.

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

vercel/next.js (next)

v16.4.5

Compare Source

This release contains security fixes for the following advisories:

Moderate

v16.4.4

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary. The announced security released for November will be published tomorrow.

Core Changes
  • [lts-active] test: disable the reads fallback params after a client navigation deployment test (#​100668)
  • [lts-active] Reload on missed Turbopack startup CSS updates (#​100619)
  • [lts-active] Revert "Optimize strict module factory chunks (#​98421)" (#​100866)
  • [lts-active] Emit the Turbopack shared-runtime bootstrap in the PPR resume so it gets the CSP nonce (#​100907)
  • [lts-active] [ci] Pin deploy test deployments to Node.js 22.x (#​100886)
  • [lts-active] fix(analyze): use route summaries as the analyzer route index (#​100974)
  • [lts-active] Use fast-jwt instead of jsonwebtoken (#​100885)
Credits

Huge thanks to @​icyJoseph, @​mischnic, @​wbinnssmith, @​lukesandberg, and @​eps1lon for helping!

v16.4.3

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
Credits

Huge thanks to @​mischnic, @​lukesandberg, @​acdlite, @​eps1lon, and @​sokra for helping!

v16.4.2

Compare Source

What's Changed

Full Changelog: vercel/next.js@v16.4.1...v16.4.2

v16.4.1

Compare Source

This release contains security fixes for the following advisories:

Critical:

High:

v16.4.0

Compare Source

Check out the 16.4 announcement post to get an overview of the changes.

Core Changes
  • Show compiler plugin warning in more situations: #​75682
  • fix(scripts): correct typo in rm.mjs error message: #​87015
  • docs: improve clarity and punctuation in README: #​86096
  • Fix debug build paths Pages Router support entries: #​93529
  • bundle-analyzer: record historical snapshots on each analyze run: #​93520
  • fix: detect proxy.ts correctly with compound pageExtensions: #​93246
  • feat(turbopack): support false values for resolveAlias config: #​93331
Misc Changes
  • docs: correction to dynamicParams migration: #​96624
  • docs: proxy event argument: #​96435
  • docs: remove experimental note from runtime prefetching: #​96615
  • Preserve per-segment prefetching after dynamic navigation: #​96583
  • Rename static generation stream option to waitForAllReady: #​96564
  • Remove obsolete static generation plumbing: #​96563
  • [turbopack] Drop dead writes to exports: #​96381
  • [turbopack] Ignore writes to exports after a module.exports = {} writes: #​96380
  • [turbopack] Add test for sideEffects with optimizePackageImports: #​96549
  • [turbopack] Strip leading BOM before parsing CSS: #​96678
  • Upgrade React from cbb046ab-20260731 to 7dfc7ccd-20260803: #​96550
  • docs: use relative doc links in instant-navigation error pages: #​96672
  • Turbopack: terminate failed plugin worker threads: #​96592
  • Fix HTML-limited bot matching in prerender bypass rules: #​96584
  • [ci] Fix create_release_branch for new repo permissions: #​96641
  • test: skip action module instance deploy test: #​96629
  • docs: quote the dynamicParams build error in a blockquote: #​96633
  • [react-sync] Open pull requests as the bot that authors the commits: #​96682
  • [Bench] Fixes for pure Fizz bench: #​96771
  • Derive foreground cache revalidation from the consumer: #​96731
  • Fix race when navigating Back before hydration: #​96252
  • docs: present each Skill as steps in the AI agents guide: #​96751
  • Reuse completed cache entries for the rest of a request: #​96727
  • Upgrade React from 7dfc7ccd-20260803 to 11eddecd-20260805: #​96735
  • Remove WorkStore execution mode: #​96674
  • Remove cache revalidation execution mode reads: #​96670
  • Separate App Route render and prerender pipelines: #​96662
  • Remove App Page execution mode reads: #​96660
  • test: fix missing await in css-chunking test: #​96725
  • docs (Skills): stop assuming app/ at the root and port 3000: #​96696
  • Implement next/font BeforeResolvePlugins as ImportMappingReplacement: #​95808
  • Use Tailwind Turbopack loader in create-next-app: #​96606
  • docs: instant navigation quick start with an adoption prompt: #​96663
  • Separate App Page render and prerender pipelines: #​96659
  • Move App Router execution intent to entrypoints: #​96640
  • Pass explicit render capabilities through App Render: #​96576
  • Pass explicit prefetch hint policy through App Render: #​96572
  • Replace WorkStore isStaticGeneration with executionMode: #​96570
  • docs: document ! exclusion and src/ prefix for --debug-build-paths: #​96703
  • Change loadManifest to return undefined with handleMissing: #​96530
  • Refactor server from CacheNodeSeedData -> TransportData: #​96679
  • Unify full/partial navigation response types: #​96439
  • Unify RouteTree and CacheNodeSeedData on the client: #​96406
  • Consolidate Promise.withResolvers polyfills: #​96772
  • [ci] Open automated update pull requests with nextjs-bot: #​96683
  • Require Cache Components for Instant Navigation testing: #​96745
  • Fix use cache over- and under-invalidation in dev: #​96235
  • Fix which pages the dev server announces, and when: #​96250
  • docs: update redirected links to current targets: #​96723
  • Fix(deployment-id): prevent exception on old webkit: #​94604
  • [fragment-scroll] Remove config.experimental.appNewScrollHandler: #​95602
  • [turbopack] Enable reexport-unknown execution test: #​96774
  • ci: stop publishing @​vercel/devlow-bench: #​96887
  • fix(turbopack): name the module in the non-ESM-placeable error, and stop duplicating the importer in traces: #​96560
  • fix(turbopack): support type: 'text' in rules, and error on binding imports of non-ESM modules: #​96558

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 2bfc83d to 005c0a5 Compare October 15, 2026 03:38
@renovate renovate Bot changed the title fix(deps): update dependency next to v16.3.6 [security] fix(deps): update dependency next to v16.3.8 [security] Oct 15, 2026
@renovate
renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 005c0a5 to a914404 Compare October 27, 2026 18:23
@renovate renovate Bot changed the title fix(deps): update dependency next to v16.3.8 [security] fix(deps): update dependency next to v16.4.1 [security] Oct 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 2b5b313 to e027231 Compare November 11, 2026 20:59
@renovate
renovate Bot force-pushed the renovate/npm-next-vulnerability branch from e027231 to 0f83820 Compare November 16, 2026 19:03
@renovate renovate Bot changed the title fix(deps): update dependency next to v16.4.1 [security] fix(deps): update dependency next to v16.4.5 [security] Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants