Skip to content

Update dependency next to v15.5.14 [SECURITY]#159

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

Update dependency next to v15.5.14 [SECURITY]#159
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-next-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 4, 2025

This PR contains the following updates:

Package Change Age Confidence
next (source) 15.5.715.5.14 age confidence

GitHub Vulnerability Alerts

GHSA-w37m-7fhw-fmv9

A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as CVE-2025-55183.

A malicious HTTP request can be crafted and sent to any App Router endpoint that can return the compiled source code of Server Functions. This could reveal business logic, but would not expose secrets unless they were hardcoded directly into Server Function code.

GHSA-mwv6-3258-q52c

A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as CVE-2025-55184.

A malicious HTTP request can be crafted and sent to any App Router endpoint that, when deserialized, can cause the server process to hang and consume CPU. This can result in denial of service in unpatched environments.

GHSA-h25m-26qc-wcjf

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.

CVE-2025-59471

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.

CVE-2026-29057

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.

CVE-2026-27980

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)

Release Notes

vercel/next.js (next)

v15.5.14

Compare Source

v15.5.13

Compare Source

v15.5.12

Compare Source

[!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 applying the turbopack changes.

v15.5.11

Compare Source

[!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 (#​85529)
  • fix: ensure LRU cache items have minimum size of 1 to prevent unbounded growth (#​89134)
  • Turbopack: fix NFT tracing of sharp 0.34 (#​82340)
  • Turbopack: support pattern into exports field (#​82757)
  • NFT tracing fixes (#​84155 and #​85323)
  • Turbopack: validate CSS without computing all paths (#​83810)
  • feat: implement LRU cache with invocation ID scoping for minimal mode response cache (#​89129)
Credits

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

v15.5.10

Compare Source

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

v15.5.9

Compare Source

v15.5.8

Compare Source


Configuration

📅 Schedule: Branch creation - "" (UTC), 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 52a6531 to 8770f79 Compare August 31, 2025 08:56
@renovate renovate bot changed the title Update dependency next to v15.3.3 [SECURITY] Update dependency next to v15.4.7 [SECURITY] Aug 31, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 8770f79 to d96a8b3 Compare September 25, 2025 20:15
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from d96a8b3 to 3d94238 Compare October 25, 2025 07:17
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 3d94238 to e4530ba Compare November 11, 2025 02:01
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from e4530ba to b8a246a Compare November 18, 2025 22:40
@renovate renovate bot changed the title Update dependency next to v15.4.7 [SECURITY] Update dependency next to v15.4.7 [SECURITY] - autoclosed Dec 9, 2025
@renovate renovate bot closed this Dec 9, 2025
@renovate renovate bot deleted the renovate/npm-next-vulnerability branch December 9, 2025 14:54
@renovate renovate bot changed the title Update dependency next to v15.4.7 [SECURITY] - autoclosed Update dependency next to v15.5.8 [SECURITY] Dec 12, 2025
@renovate renovate bot reopened this Dec 12, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from b8a246a to b1c89e9 Compare December 12, 2025 02:48
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from b1c89e9 to 56e9f79 Compare February 2, 2026 17:09
@renovate renovate bot changed the title Update dependency next to v15.5.8 [SECURITY] Update dependency next to v16 [SECURITY] Feb 2, 2026
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 56e9f79 to a557d6d Compare February 5, 2026 17:52
@renovate renovate bot changed the title Update dependency next to v16 [SECURITY] Update dependency next to v15.5.10 [SECURITY] Feb 5, 2026
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from a557d6d to 3dc4b3f Compare March 22, 2026 00:43
@renovate renovate bot changed the title Update dependency next to v15.5.10 [SECURITY] Update dependency next to v15.5.13 [SECURITY] Mar 22, 2026
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 3dc4b3f to e1b2650 Compare March 23, 2026 17:12
@renovate renovate bot changed the title Update dependency next to v15.5.13 [SECURITY] Update dependency next to v15.5.14 [SECURITY] Mar 23, 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