chore(deps): update dependency next to v16 [security] by renovate[bot] · Pull Request #220 · RevoTale/next-scroll-restorer

renovate · 2026-03-21T23:41:31Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
next (source)	`15.5.10` → `16.2.6`

Next.js: HTTP request smuggling in rewrites

CVE-2026-29057 / GHSA-ggv3-7p47-pfv8

More information

Details

Summary

When Next.js rewrites proxy traffic to an external backend, a crafted DELETE/OPTIONS request using Transfer-Encoding: chunked could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes.

Impact

An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel.

Patches

The vulnerability originated in an upstream library vendored by Next.js. It is fixed by updating that dependency’s behavior so content-length: 0 is added only when both content-length and transfer-encoding are absent, and transfer-encoding is no longer removed in that code path.

Workarounds

If upgrade is not immediately possible:

Block chunked DELETE/OPTIONS requests on rewritten routes at your edge/proxy.
Enforce authentication/authorization on backend routes per our security guidance.

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

Next.js: Unbounded next/image disk cache growth can exhaust storage

CVE-2026-27980 / GHSA-3x4c-7xq6-9pq8

More information

Details

Summary

The default Next.js image optimization disk cache (/_next/image) did not have a configurable upper bound, allowing unbounded cache growth.

Impact

An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. Note that this does not impact platforms that have their own image optimization capabilities, such as Vercel.

Patches

Fixed by adding an LRU-backed disk cache with images.maximumDiskCacheSize, including eviction of least-recently-used entries when the limit is exceeded. Setting maximumDiskCacheSize: 0 disables disk caching.

Workarounds

If upgrade is not immediately possible:

Periodically clean .next/cache/images.
Reduce variant cardinality (e.g., tighten values for images.localPatterns, images.remotePatterns, and images.qualities)

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 has a Denial of Service with Server Components

GHSA-q4gf-8mx6-v5v3

More information

Details

A vulnerability affects certain React Server Components packages for versions 19.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23869. You can read more about this advisory our this changelog.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage. This can result in denial of service in unpatched environments.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

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

Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

CVE-2026-44574 / GHSA-492v-c6pp-mqqv

More information

Details

Impact

Applications that rely on middleware to protect dynamic routes can be vulnerable to authorization bypass. In affected deployments, specially crafted query parameters can alter the dynamic route value seen by the page while leaving the visible path unchanged, which can allow protected content to be rendered without passing the expected middleware check.

Fix

We now only honor internal route-parameter normalization in trusted routing flows and ignore externally supplied parameter encodings that should never have been accepted from ordinary requests.

Workarounds

If you cannot upgrade immediately, enforce authorization in route or page logic instead of relying solely on middleware path matching.

Severity

CVSS Score: 8.1 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

References

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

Next.js Vulnerable to Denial of Service with Server Components

GHSA-8h8q-6873-q5fj

More information

Details

A vulnerability affects certain React Server Components packages for versions 19.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23870.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage. This can result in denial of service in unpatched environments.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

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

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

CVE-2026-44575 / GHSA-267c-6grr-h53f

More information

Details

Impact

App Router applications that rely on middleware or proxy-based checks for authorization can allow unauthorized access through transport-specific route variants used for segment prefetching. In affected configurations, specially crafted .rsc and segment-prefetch URLs can resolve to the same page without being matched by the intended middleware rule, which can allow protected content to be reached without the expected authorization check.

Fix

We now include App Router transport variants when generating middleware matchers, so middleware protections are applied consistently to those requests as well as to the normal page URL.

Workarounds

If you cannot upgrade immediately, enforce authorization in the underlying route or page logic instead of relying solely on middleware.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

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

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

CVE-2026-44573 / GHSA-36qx-fr4f-26g5

More information

Details

Impact

Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks.

Fix

The matcher logic was updated to perform the same match as it would on a non-i18n data route.

Workarounds

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

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

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

Next.js has cross-site scripting in beforeInteractive scripts with untrusted input

CVE-2026-44580 / GHSA-gx5p-jg67-6x7h

More information

Details

Impact

Applications that use beforeInteractive scripts together with untrusted content can be vulnerable to cross-site scripting. In affected versions, serialized script content was not escaped safely before being embedded into the document, which could allow attacker-controlled input to break out of the intended script context and execute arbitrary JavaScript in a visitor's browser.

Fix

We now HTML-escape serialized beforeInteractive script content before embedding it into the page, preventing attacker-controlled content from breaking out of the inline script boundary.

Workarounds

If you cannot upgrade immediately, do not pass untrusted data into beforeInteractive scripts. If that pattern is unavoidable, sanitize or escape the content before embedding it.

Severity

CVSS Score: 6.1 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

References

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

Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades

CVE-2026-44578 / GHSA-c4j6-fc7j-m34r

More information

Details

Impact

Self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected.

Fix

We now apply the same safety checks to WebSocket upgrade handling that already existed for normal HTTP requests, so upgrade requests are only proxied when routing has explicitly marked them as safe external rewrites.

Workarounds

If you cannot upgrade immediately, do not expose the origin server directly to untrusted networks. If WebSocket upgrades are not required, block them at your reverse proxy or load balancer, and restrict origin egress to internal networks and metadata services where possible.

Severity

CVSS Score: 8.6 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

References

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

Next.js vulnerable to cache poisoning in React Server Component responses

CVE-2026-44576 / GHSA-wfc6-r584-vfw7

More information

Details

Impact

Applications using React Server Components can be vulnerable to cache poisoning when shared caches do not correctly partition response variants. Under affected conditions, an attacker can cause an RSC response to be served from the original URL and poison shared cache entries so later visitors receive component payloads instead of the expected HTML.

Fix

We now validate and interpret RSC request headers consistently across request classification and rendering, and we enforce the intended cache-busting behavior so RSC payloads are not unexpectedly served from the original URL.

Workarounds

If you cannot upgrade immediately, ensure your CDN or reverse proxy keys on the relevant RSC request headers and honors Vary, or disable shared caching for affected App Router and RSC responses.

Severity

CVSS Score: 5.4 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L

References

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

Next.js has a Denial of Service in the Image Optimization API

CVE-2026-44577 / GHSA-h64f-5h5j-jqjh

More information

Details

Impact

When self-hosting Next.js with the default image loader, the Image Optimization API fetches local images entirely into memory without enforcing a maximum size limit. An attacker could cause out-of-memory conditions by requesting large local assets from the /_next/image endpoint that match the images.localPatterns configuration (by default, all patterns are allowed).

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

Fix

We now apply response size limits consistently to internal image fetches, not just external ones, and fail oversized responses before they can exhaust process memory.

This can be adjusted using the images.maximumResponseBody configuration.

Workarounds

If you cannot upgrade immediately, avoid routing large local assets through /_next/image, disable image optimization for large or untrusted local files, or block image optimization access to those assets at the edge.

You can disable using the images.localPatterns: [] configuration. This will still allow fetching remote images (which is not impacted).

Severity

CVSS Score: 5.9 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References

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

Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces

CVE-2026-44581 / GHSA-ffhc-5mcf-pf4q

More information

Details

Impact

App Router applications that rely on CSP nonces can be vulnerable to stored cross-site scripting when deployed behind shared caches. In affected versions, malformed nonce values derived from request headers could be reflected into rendered HTML in an unsafe way, allowing an attacker to poison cached responses and cause script execution for later visitors.

Fix

We now reject or ignore malformed nonce values before they are embedded into HTML and apply stricter nonce sanitization so request-derived nonce data cannot break out of the intended attribute context.

Workarounds

If you cannot upgrade immediately, strip inbound Content-Security-Policy request headers from untrusted traffic.

Severity

CVSS Score: 4.7 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

References

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

Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting

CVE-2026-44582 / GHSA-vfv6-92ff-j949

More information

Details

Impact

React Server Component responses can be vulnerable to cache poisoning in deployments that rely on shared caches with insufficient response partitioning. In affected conditions, collisions in the _rsc cache-busting value can allow an attacker to poison cache entries so users receive the wrong response variant for a given URL.

Fix

We strengthened the _rsc cache-busting mechanism to make practical collisions significantly harder and to better separate response variants that should not share cache entries.

Workarounds

If you cannot upgrade immediately, ensure intermediary caches correctly honor Vary for RSC-related request headers, or disable shared caching for affected RSC responses until you can deploy a patched release.

Severity

CVSS Score: 3.7 / 10 (Low)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

References

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

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up

CVE-2026-45109 / GHSA-26hh-7cqf-hhc6

More information

Details

Impact

It was found that the fix addressing CVE-2026-44575 did not apply to middleware.ts with Turbopack. Refer to CVE-2026-44575 for further details.

References

CVE CVE-2026-44575

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

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

Next.js's Middleware / Proxy redirects can be cache-poisoned

CVE-2026-44572 / GHSA-3g8h-86w9-wvmq

More information

Details

Impact

Next.js uses the x-nextjs-data request header for internal data requests. On affected versions, an external client could send this header on a normal request to a path handled by middleware that returns a redirect.

When that happened, the middleware/proxy could treat the request as a data request and replace the standard Location redirect header with the internal x-nextjs-redirect header. Browsers do not follow x-nextjs-redirect, so the response became an unusable redirect for normal clients.

If the application was deployed behind a CDN or reverse proxy that caches 3xx responses without varying on this header, a single attacker request could poison the cached redirect response for the affected path. Subsequent visitors could then receive a cached redirect response without a Location header, causing a denial of service for that redirect path until the cache entry expired or was purged.

Affected scenarios

This affects applications that:

use middleware or proxy redirects
are deployed behind a caching CDN or reverse proxy
allow 3xx responses on those paths to be cached without differentiating internal data requests from normal requests

Fix

The fix stops trusting x-nextjs-data by itself for middleware redirect handling. A request is now treated as an internal data request only when it is validated as such by internal routing state, preserving legitimate data-request redirect behavior while preventing external header injection from changing normal redirect responses.

Workarounds

Before upgrading, users can reduce risk by:

configuring the CDN or reverse proxy to vary its cache key on x-nextjs-data for affected responses

Severity

CVSS Score: 3.7 / 10 (Low)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

References

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

Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components

CVE-2026-44579 / GHSA-mg66-mrh9-m8jx

More information

Details

Impact

Applications using Partial Prerendering through the Cache Components feature can be vulnerable to connection exhaustion through crafted POST requests to a server action. In affected configurations, a malicious request can trigger a request-body handling deadlock that leaves connections open for an extended period, consuming file descriptors and server capacity until legitimate users are denied service.

Fix

We now treat the header used for resuming Partial Prerendered requests as an internal-only header and strip it from untrusted incoming requests. This header should never be accepted directly from external clients.

Workarounds

If you cannot upgrade immediately, block requests that would be handled by Next.js if they contain the Next-Resume header at the edge.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

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

Release Notes

vercel/next.js (next)

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

Core Changes

Upgrade to swc 54 (#88207)
implement LRU cache with invocation ID scoping for minimal mode response cache (#88509)
tweak LRU sentinel key (#89123)

Credits

Huge thanks to @mischnic, @wyattjoh, and @ztanner for helping!

`v16.1.5`

Compare Source

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472
https://vercel.com/changelog/summary-of-cve-2026-23864

`v16.1.4`

Compare Source

`v16.1.3`

Compare Source

`v16.1.2`

Compare Source

`v16.1.1`

Compare Source

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

Core Changes

Turbopack: Create junction points instead of symlinks on Windows (#87606)

Credits

Huge thanks to @sokra and @ztanner for helping!

`v16.1.0`

Compare Source

`v16.0.11`

Compare Source

Please see this changelog for more information about this security patch.

`v16.0.10`

Compare Source

`v16.0.9`

Compare Source

`v16.0.8`

Compare Source

`v16.0.7`

Compare Source

`v16.0.6`

Compare Source

`v16.0.5`

Compare Source

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

Core Changes

fix(nodejs-middleware): await for body cloning to be properly finalized (#85418)

Credits

Huge thanks to @lucasadrianof for helping!

`v16.0.4`

Compare Source

`v16.0.3`

Compare Source

Core Changes

fix: Rspack throw error when using ForceCompleteRuntimePlugin: #85221
fix: build CLI output not displaying Proxy (Middleware) when nodejs runtime: #85403
fix: staleTimes.static should consistently enforce a 30s minimum: #85479
[turbopack] fix build of empty entries of pages: #84873
Cache the head separately from the route tree: #84724
Allow inspecting dev server on default port with next dev --inspect: #85037
Avoid proxying React modules through workUnitStore: #85486
fix: redirect should always return updated router state: #85533
Upgrade React from b4455a6e-20251027 to 4f931700-20251029: #85518
[turbopack] Move generation of cacheLife types out of the webpack plugin and into the dev bundler directly: #85539
Ensure user-space stack frame for 'use cache' in page/layout component: #85519
Update parallel routes in build-complete: #85546
fully remove clientSegmentCache flag: #85541
[turbopack] Support relative paths in turbopack source maps.: #85146
Release unnecessary memory on hydration finish: #84967
Preserve interception markers in parameter types: #85526
move segment cache entries to top level segment-cache dir: #85542
Upgrade React from 4f931700-20251029 to 561ee24d-20251101: #85670
[devtools] Remove title from preferences: #85698
Update font data: #85708
Don't invalidate hot reloader excessively during dev server boot: #85732
[codemod] fix: next-lint-to-eslint-cli did not handle 'next' plugin: #85749
Upgrade React from 561ee24d-20251101 to 67f7d47a-20251103: #85762
Tracing: Fix memory leak in span map: #85529
Fix documentation typo in refresh function: #85696
fix: eslint-config-next types was exporting to dist/src: #85768
Upgrade React from 67f7d47a-20251103 to f646e8ff-20251104: #85772
remove unused RSC payload property: #85746
[runtime prefetching]: fix runtime prefetching when deployed: #85595
Turbopack: next build --analyze: #85197
Build: Log amount of workers during static generation: #85706
Upgrade React from f646e8ff-20251104 to dd048c3b-20251105: #85819
Sync devFallbackParams when generateStaticParams change: #85741
chore: upgrade rspack 1.6.0: #84210
[mcp] get_routes mcp tool: #85773
Split each path param into a separate cache key : #85758
[turbopack] change server source maps in production to use relative paths: #85576
fix: skip collecting metadata for app-error in webpack: #85892
fix: support root span attributes with a custom server: #85521
fix isDynamicRSC condition when deployed: #85919
[turbopack] Make it possible to synchronously access native bindings: #85787
Upgrade React from dd048c3b-20251105 to fa50caf5-20251107: #85906
Fix telemetry event loss on build failures and server shutdown: #85867
Remove one stack frame from 'use cache' call stacks: #85966
Upgrade React from fa50caf5-20251107 to 52684925-20251110: #85980
Deployment adapter: fix metadata for "/" route: #85820
Enable React's default Transition indicator behind a flag: #86000
update routes-manifest to include whether app has pages routes: #86051

Misc Changes

chore: Add opt-level = s for not frequently used crates: #85426
[test] Deflake cache-components-allow-otel-spans: #85466
[test] Move remaining experimental.cacheLife: #85467
Turbopack: chore: Remove mopa dependency in turbo-tasks (2nd attempt): #85286
Update Proxy docs: #85439
[CNA] Do not prompt for Turbopack: #85404
Clean up new release process: #85458
Update E2E tests workflow: #85485
Update E2E deploy tests manifest: #85483
docs: example are incorrect async function exports only: #85453
[test] Handle CLI assertions where no "Compiling..." log is present: #85499
[test] Speed up refresh test: #85505
[test] Add test cases for dynamic caches without suspense boundaries: #85500
docs: Routes are wrapped w/ Activity in Cache Components: #85309
docs: GET handler behavior under cache components: #85389
[test] Avoid needless start/stop from using createSandbox: #85507
[test] Use --debug-build-paths instead of NEXT_PRIVATE_APP_PATHS: #85504
docs: revalidateTag requires second argument: #85284
Refactor GTM implementation to support google tag gateway: #81011
Update Rspack production test manifest: #85494
Update Rspack development test manifest: #85495
[docs] Fix a typo: #85492
[test] Regenerate tsconfig.json files: #85515
[Turbopack] clean up completion.rs a bit: #84863
[test] Remove maxRetries and hardError parameters: #85536
Turbopack: remove the .into() alias to .cell(): #85516
[test] Consolidate identical snapshots across different bundlers: #85532
[turbopack] Change where cells are created in resolve_raw to make cell allocation order deterministic.: #85525
Turbopack: Make tasks deterministic: #85524
[test] Separate act and assertions: #85508
[test] assert* -> waitFor* when the util is not instant: #85450
Turbopack: move whole_app_module_graphs to top level: #84897
[test] Bail on sending requests to Next.js instance if it's no longer available: #85557
[test] Deflake tests comparing two random numbers: #85571
[test] Disallow custom RegExp-like implementations in check: #85537
[test] Deflake prerender suite: #85563
Turbopack: chore: Remove some dead MagicAny serialization code from turbo_tasks::value: #85577
[test]: fix broken scroll restoration test: #85599
[test] Deflake nested after() tests: #85566
[test] Stop installing unused dependencies: #85569
[test] Consider test/integration/ in flake detection tests: #85590
Turbopack: more checks on verify_serialization: #84952
Turbopack: add track_caller to improve panics: #85565
Turbopack: add verify_determinism feature to check if tasks are deterministic: #85559
docs: cache life rework: #85224
Turbopack: fix hanging dev server and builds with fs cache: #85606
Turbopack: Fix compound assignment expression evaluation (#85478): #85593
Turbopack: fix Scope holding Arc too long: #85611
[ci] Improve change detection logic in run-for-change script: #85619
[test] Ignore in deploy tests if a child process isn't available: #85636
Turbopack: add size_hint and len for Chunk iterator: #85622
[test]: move resume-data-cache to e2e test: #85647
Update Rspack development test manifest: #85662
Update Rspack production test manifest: #85661
Update Rspack production test manifest: #85688
Update Rspack development test manifest: #85689
[test] Deflake root-optional-revalidate: #85584
docs: fix generateImageMetadata example to use normal params object: #85658
Turbopack: Upgrade image crate: #85084
docs: update multi sitemap argumenmt type: #85701
[test] Move all files to .ts (6/6): #85641
Turbopack: add a batch add method to the storage: #84270
docs: recommend reverse-proxy when self-hosting: #85650
[test] Deflake prefetching.stale-times: #85733
[test] Deflake custom cache handler test: #85610
[test] Allow CLI integration test to be retryable: #85586
docs: update docs to mention ESLint as default: #85740
docs(next.config): this docs should remove ".mts" is not supported.: #85716
Turbopack: cleanup StyleSheetLike: #85718
Turbopack: disable tree shaking for tracing: #85722
[test] Move all files to .ts (3/6): #85638
[test] Move all files to .ts (2/6): #85637
[test] Move all files to .ts (1/6): #85634
docs: generateSitemap passes id as promise: #85767
[test] Move all files to .ts (4/6): #85639
docs: disclosure on path-to-regexp: #85629
chore: update rspack binding to 1.6.0: #85717
Turbopack: trace worker_t

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- ""
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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 Bot force-pushed the renovate/npm-next-vulnerability branch from eda84a4 to cb185ce Compare March 23, 2026 17:58

renovate Bot changed the title ~~chore(deps): update dependency next to v15.5.13 [security]~~ chore(deps): update dependency next to v15.5.14 [security] Mar 23, 2026

renovate Bot changed the title ~~chore(deps): update dependency next to v15.5.14 [security]~~ chore(deps): update dependency next to v15.5.14 [security] - autoclosed Mar 27, 2026

renovate Bot closed this Mar 27, 2026

renovate Bot deleted the renovate/npm-next-vulnerability branch March 27, 2026 02:06

renovate Bot changed the title ~~chore(deps): update dependency next to v15.5.14 [security] - autoclosed~~ chore(deps): update dependency next to v15.5.14 [security] Mar 30, 2026

renovate Bot reopened this Mar 30, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from 0a9088d to 080d2cb Compare April 1, 2026 17:46

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from c776ebd to 62e56fc Compare April 13, 2026 23:34

renovate Bot changed the title ~~chore(deps): update dependency next to v15.5.14 [security]~~ chore(deps): update dependency next to v15.5.15 [security] Apr 13, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 62e56fc to c9f8ec1 Compare April 15, 2026 10:23

renovate Bot changed the title ~~chore(deps): update dependency next to v15.5.15 [security]~~ chore(deps): update dependency next to v16 [security] Apr 15, 2026

renovate Bot changed the title ~~chore(deps): update dependency next to v16 [security]~~ chore(deps): update dependency next to v16 [security] - autoclosed Apr 27, 2026

renovate Bot closed this Apr 27, 2026

renovate Bot changed the title ~~chore(deps): update dependency next to v16 [security] - autoclosed~~ chore(deps): update dependency next to v16 [security] Apr 27, 2026

renovate Bot reopened this Apr 27, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from af38bb8 to 6384325 Compare April 29, 2026 16:29

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from 0be996f to 6490bc5 Compare May 18, 2026 09:35

chore(deps): update dependency next to v16 [security]

3decd1c

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 6490bc5 to 3decd1c Compare May 28, 2026 20:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update dependency next to v16 [security]#220

chore(deps): update dependency next to v16 [security]#220
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-next-vulnerability

renovate Bot commented Mar 21, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Mar 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Next.js: HTTP request smuggling in rewrites

Details

Summary

Impact

Patches

Workarounds

Severity

References

Next.js: Unbounded next/image disk cache growth can exhaust storage

Details

Summary

Impact

Patches

Workarounds

Severity

References

Next.js has a Denial of Service with Server Components

Details

Severity

References

Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

Details

Impact

Fix

Workarounds

Severity

References

Next.js Vulnerable to Denial of Service with Server Components

Details

Severity

References

Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

Details

Impact

Fix

Workarounds

Severity

References

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

Details

Impact

Fix

Workarounds

Severity

References

Next.js has cross-site scripting in beforeInteractive scripts with untrusted input

Details

Impact

Fix

Workarounds

Severity

References

Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades

Details

Impact

Fix

Workarounds

Severity

References

Next.js vulnerable to cache poisoning in React Server Component responses

Details

Impact

Fix

Workarounds

Severity

References

Next.js has a Denial of Service in the Image Optimization API

Details

Impact

Fix

Workarounds

Severity

References

Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces

Details

Impact

Fix

renovate Bot commented Mar 21, 2026 •

edited

Loading