Skip to content

fix(deps): update dependency next to v15.5.13 [security]#317

Merged
davidzhao merged 1 commit intomainfrom
renovate/npm-next-vulnerability
Mar 22, 2026
Merged

fix(deps): update dependency next to v15.5.13 [security]#317
davidzhao merged 1 commit intomainfrom
renovate/npm-next-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 28, 2026

This PR contains the following updates:

Package Change Age Confidence
next (source) 15.5.915.5.13 age confidence

GitHub Vulnerability Alerts

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.

Release Notes

vercel/next.js (next)

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:


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

@vercel
Copy link

vercel bot commented Jan 28, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sandbox-voice-assistant Ready Ready Preview Mar 22, 2026 1:08am

Request Review

@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 3fd4f7e to 79f174c Compare January 29, 2026 18:51
@renovate renovate bot changed the title fix(deps): update dependency next to v15.5.10 [security] fix(deps): update dependency next to v16 [security] Jan 29, 2026
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 79f174c to 610d606 Compare February 5, 2026 17:39
@renovate renovate bot changed the title fix(deps): update dependency next to v16 [security] fix(deps): update dependency next to v15.5.10 [security] Feb 5, 2026
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 610d606 to ddf5a13 Compare February 13, 2026 21:43
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from ddf5a13 to 69bb070 Compare February 18, 2026 14:24
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 69bb070 to 01a7332 Compare February 24, 2026 20:05
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 01a7332 to 0652c83 Compare February 27, 2026 18:30
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 0652c83 to ba33652 Compare March 22, 2026 01:07
@renovate renovate bot changed the title fix(deps): update dependency next to v15.5.10 [security] fix(deps): update dependency next to v15.5.13 [security] Mar 22, 2026
@davidzhao davidzhao merged commit 73a3ef5 into main Mar 22, 2026
5 checks passed
@davidzhao davidzhao deleted the renovate/npm-next-vulnerability branch March 22, 2026 04:19
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.

1 participant