fix(deps): update dependency next to v15 [security] by renovate[bot] · Pull Request #691 · powerkernel/power-web

renovate · 2026-02-15T05:15:20Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
next (source)	`14.2.35` → `15.5.21`

Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components

GHSA-h25m-26qc-wcjf

More information

Details

A vulnerability affects certain React Server Components packages for versions 19.0.x, 19.1.x, and 19.2.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-23864.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage, out-of-memory exceptions, or server crashes. 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 self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration

CVE-2025-59471 / GHSA-9g9p-9gw9-jx7f

More information

Details

A DoS vulnerability exists in self-hosted Next.js applications that have remotePatterns configured for the Image Optimizer. The image optimization endpoint (/_next/image) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires that remotePatterns is configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain.

Strongly consider upgrading to 15.5.10 and 16.1.5 to reduce risk and prevent availability issues in Next applications.

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: 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 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 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 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 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 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 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 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 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'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: Denial of Service in App Router using Server Actions

CVE-2026-64641 / GHSA-m99w-x7hq-7vfj

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 disclosure of internal Server Function endpoints

CVE-2026-64643 / GHSA-955p-x3mx-jcvp

More information

Details

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.

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: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

CVE-2026-64645 / GHSA-p9j2-gv94-2wf4

More information

Details

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-]+)'.

Severity

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

References

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

Next.js: Unbounded Server Action payload in Edge runtime

CVE-2026-64646 / GHSA-4c39-4ccg-62r3

More information

Details

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.

Severity

CVSS Score: 6.3 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/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: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences

CVE-2026-64647 / GHSA-4633-3j49-mh5q

More information

Details

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.

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: Cache confusion of response bodies for requests with bodies

CVE-2026-64648 / GHSA-68g3-v927-f742

More information

Details

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.

Severity

CVSS Score: 6.0 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/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: Server-Side Request Forgery in Server Actions on custom servers

CVE-2026-64649 / GHSA-89xv-2m56-2m9x

More information

Details

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

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

#### References
- [https://github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x)
- [https://github.com/vercel/next.js/commit/b51206321854193208c0805ba42acc49287f942b](https://redirect.github.com/vercel/next.js/commit/b51206321854193208c0805ba42acc49287f942b)
- [https://github.com/vercel/next.js/commit/e3e5666ccead3a15162793d697af5e48b7cc0498](https://redirect.github.com/vercel/next.js/commit/e3e5666ccead3a15162793d697af5e48b7cc0498)
- [https://github.com/vercel/next.js/releases/tag/v15.5.21](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.21)
- [https://github.com/vercel/next.js/releases/tag/v16.2.11](https://redirect.github.com/vercel/next.js/releases/tag/v16.2.11)
- [https://github.com/advisories/GHSA-89xv-2m56-2m9x](https://redirect.github.com/advisories/GHSA-89xv-2m56-2m9x)

This data is provided by the [GitHub Advisory Database](https://redirect.github.com/advisories/GHSA-89xv-2m56-2m9x) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Release Notes

<details>
<summary>vercel/next.js (next)</summary>

### [`v15.5.21`](https://redirect.github.com/vercel/next.js/compare/v15.5.20...v15.5.21)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.20...v15.5.21)

### [`v15.5.20`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.20)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.19...v15.5.20)

Contains no changes except publishing `@next/swc-wasm-web` which was accidentally not published since 15.5.15.

### [`v15.5.19`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.19): 15.5.19

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.18...v15.5.19)

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

##### Core Changes

- \[15.5.x] Don't drop `FormData` entries ([#&#8203;94244](https://redirect.github.com/vercel/next.js/issues/94244))

##### Other

- \[15.5.x] Fix CI ([#&#8203;94281](https://redirect.github.com/vercel/next.js/issues/94281))

##### Credits

Huge thanks to [@&#8203;eps1lon](https://redirect.github.com/eps1lon) for helping!

### [`v15.5.18`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.18)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.16...v15.5.18)

This release contains security fixes for the following advisories:

High:

- [GHSA-8h8q-6873-q5fj: Denial of Service with Server Components](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-8h8q-6873-q5fj)
- [GHSA-267c-6grr-h53f: Middleware / Proxy bypass in App Router applications via segment-prefetch routes](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-267c-6grr-h53f)
- [GHSA-26hh-7cqf-hhc6: Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-26hh-7cqf-hhc6)
- [GHSA-mg66-mrh9-m8jx: Denial of Service via connection exhaustion in applications using Cache Components](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-mg66-mrh9-m8jx)
- [GHSA-492v-c6pp-mqqv: Middleware / Proxy bypass through dynamic route parameter injection](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-492v-c6pp-mqqv)
- [GHSA-c4j6-fc7j-m34r: Server-side request forgery in applications using WebSocket upgrades](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-c4j6-fc7j-m34r)
- [GHSA-36qx-fr4f-26g5: Middleware / Proxy bypass in Pages Router applications using i18n](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5)

Moderate:

- [GHSA-ffhc-5mcf-pf4q: Cross-site scripting in App Router applications using CSP nonces](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-ffhc-5mcf-pf4q)
- [GHSA-gx5p-jg67-6x7h: Cross-site scripting in beforeInteractive scripts with untrusted input](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-gx5p-jg67-6x7h)
- [GHSA-h64f-5h5j-jqjh: Denial of Service in the Image Optimization API](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh)
- [GHSA-wfc6-r584-vfw7: Cache poisoning in React Server Component responses](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-wfc6-r584-vfw7)

Low:

- [GHSA-vfv6-92ff-j949: Cache poisoning via collisions in React Server Component cache-busting](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949)
- [GHSA-3g8h-86w9-wvmq: Middleware / Proxy redirects can be cache-poisoned](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq)

### [`v15.5.16`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.16)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.15...v15.5.16)

This release contains security fixes for the following advisories:

High:

- [GHSA-8h8q-6873-q5fj: Denial of Service with Server Components](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-8h8q-6873-q5fj)
- [GHSA-267c-6grr-h53f: Middleware / Proxy bypass in App Router applications via segment-prefetch routes](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-267c-6grr-h53f)
- [GHSA-mg66-mrh9-m8jx: Denial of Service via connection exhaustion in applications using Cache Components](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-mg66-mrh9-m8jx)
- [GHSA-492v-c6pp-mqqv: Middleware / Proxy bypass through dynamic route parameter injection](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-492v-c6pp-mqqv)
- [GHSA-c4j6-fc7j-m34r: Server-side request forgery in applications using WebSocket upgrades](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-c4j6-fc7j-m34r)
- [GHSA-36qx-fr4f-26g5: Middleware / Proxy bypass in Pages Router applications using i18n](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5)

Moderate:

- [GHSA-ffhc-5mcf-pf4q: Cross-site scripting in App Router applications using CSP nonces](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-ffhc-5mcf-pf4q)
- [GHSA-gx5p-jg67-6x7h: Cross-site scripting in beforeInteractive scripts with untrusted input](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-gx5p-jg67-6x7h)
- [GHSA-h64f-5h5j-jqjh: Denial of Service in the Image Optimization API](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-h64f-5h5j-jqjh)
- [GHSA-wfc6-r584-vfw7: Cache poisoning in React Server Component responses](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-wfc6-r584-vfw7)

Low:

- [GHSA-vfv6-92ff-j949: Cache poisoning via collisions in React Server Component cache-busting](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949)
- [GHSA-3g8h-86w9-wvmq: Middleware / Proxy redirects can be cache-poisoned](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq)

### [`v15.5.15`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.15)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.14...v15.5.15)

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

<https://vercel.com/changelog/summary-of-cve-2026-23869>

### [`v15.5.14`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.14)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.13...v15.5.14)

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

##### Core Changes

- feat(next/image): add lru disk cache and images.maximumDiskCacheSize ([#&#8203;91660](https://redirect.github.com/vercel/next.js/issues/91660))
- Fix(pages-router): restore Content-Length and ETag for /\_next/data/ JSON responses ([#&#8203;90304](https://redirect.github.com/vercel/next.js/issues/90304))

##### Credits

Huge thanks to [@&#8203;styfle](https://redirect.github.com/styfle) and [@&#8203;lllomh](https://redirect.github.com/lllomh) for helping!

### [`v15.5.13`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.13)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.12...v15.5.13)

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

##### Core Changes

- fix: patch http-proxy to prevent request smuggling in rewrites (See: [CVE-2026-29057](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-ggv3-7p47-pfv8))

##### Credits

Huge thanks to [@&#8203;ztanner](https://redirect.github.com/ztanner) for helping!

### [`v15.5.12`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.12)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.11...v15.5.12)

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

- fix unlock in publish-native

This is a re-release of [v15.5.11](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.11) applying the turbopack changes.

### [`v15.5.11`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.11)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.10...v15.5.11)

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

##### Core Changes

- Tracing: Fix memory leak in span map ([#&#8203;85529](https://redirect.github.com/vercel/next.js/issues/85529))
- fix: ensure LRU cache items have minimum size of 1 to prevent unbounded growth ([#&#8203;89134](https://redirect.github.com/vercel/next.js/issues/89134))
- Turbopack: fix NFT tracing of sharp 0.34 ([#&#8203;82340](https://redirect.github.com/vercel/next.js/issues/82340))
- Turbopack: support pattern into exports field ([#&#8203;82757](https://redirect.github.com/vercel/next.js/issues/82757))
- NFT tracing fixes ([#&#8203;84155](https://redirect.github.com/vercel/next.js/issues/84155) and [#&#8203;85323](https://redirect.github.com/vercel/next.js/issues/85323))
- Turbopack: validate CSS without computing all paths ([#&#8203;83810](https://redirect.github.com/vercel/next.js/issues/83810))
- feat: implement LRU cache with invocation ID scoping for minimal mode response cache ([#&#8203;89129](https://redirect.github.com/vercel/next.js/issues/89129))

##### Credits

Huge thanks to [@&#8203;timneutkens](https://redirect.github.com/timneutkens), [@&#8203;mischnic](https://redirect.github.com/mischnic), [@&#8203;ztanner](https://redirect.github.com/ztanner), and [@&#8203;wyattjoh](https://redirect.github.com/wyattjoh) for helping!

### [`v15.5.10`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.10)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.9...v15.5.10)

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>

### [`v15.5.9`](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.9)

[Compare Source](https://redirect.github.com/vercel/next.js/compare/v15.5.8...v15.5.9)

Please see the [Next.js Security Update](https://ne

> ✂ **Note**
> 
> PR body was truncated to here.


</details>

---

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

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/powerkernel/power-web).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My44LjUiLCJ1cGRhdGVkSW5WZXIiOiI0My4yODAuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

renovate Bot changed the title ~~fix(deps): update dependency next to v15 [security]~~ fix(deps): update dependency next to v15 [security] - autoclosed Feb 21, 2026

renovate Bot closed this Feb 21, 2026

renovate Bot deleted the renovate/npm-next-vulnerability branch February 21, 2026 01:38

renovate Bot changed the title ~~fix(deps): update dependency next to v15 [security] - autoclosed~~ fix(deps): update dependency next to v15 [security] Feb 25, 2026

renovate Bot reopened this Feb 25, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 3f83134 to 00af9bb Compare February 25, 2026 01:11

renovate Bot changed the title ~~fix(deps): update dependency next to v15 [security]~~ fix(deps): update dependency next to v15 [security] - autoclosed Mar 1, 2026

renovate Bot closed this Mar 1, 2026

renovate Bot changed the title ~~fix(deps): update dependency next to v15 [security] - autoclosed~~ fix(deps): update dependency next to v15 [security] Mar 6, 2026

renovate Bot reopened this Mar 6, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 00af9bb to d1b0609 Compare March 6, 2026 08:55

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from d1b0609 to fb8e49b Compare March 13, 2026 14:51

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 0982634 to 4639213 Compare March 23, 2026 18:27

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 4639213 to 174e575 Compare April 1, 2026 17:16

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from 477b98c to 9d37542 Compare April 14, 2026 01:09

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 9d37542 to 12f36a4 Compare April 25, 2026 08:28

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 070dbc6 to 99df5c4 Compare May 15, 2026 08:49

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 99df5c4 to 7c40602 Compare May 28, 2026 19:57

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 7c40602 to 3e3319c Compare June 11, 2026 16:52

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 47bb9fd to 86f6bf9 Compare July 16, 2026 17:44

fix(deps): update dependency next to v15 [security]

c192755

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 86f6bf9 to c192755 Compare July 27, 2026 01:50

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update dependency next to v15 [security] - #691

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

renovate Bot commented Feb 15, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

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

Uh oh!

Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components

Details

Severity

References

Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration

Details

Severity

References

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 vulnerable to cache poisoning in React Server Component responses

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 Pages Router applications using i18n

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 has a Denial of Service in the Image Optimization API

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 cache poisoning via collisions in React Server Component cache-busting

Details

Impact

Fix

Workarounds

Severity

References

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

Details

renovate Bot commented Feb 15, 2026 •

edited

Loading