Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 4, 2025

This PR contains the following updates:

Package Change Age Confidence
next (source) ^15.5.6^16.0.0 age confidence

GitHub Vulnerability Alerts

GHSA-9qr9-h5gf-34mp

A vulnerability affects certain React packages1 for versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 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-55182.

Fixed in:
React: 19.0.1, 19.1.2, 19.2.1
Next.js: 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7, 15.6.0-canary.58, 16.1.0-canary.12+

The vulnerability also affects experimental canary releases starting with 14.3.0-canary.77. Users on any of the 14.3 canary builds should either downgrade to a 14.x stable release or 14.3.0-canary.76.

All users of stable 15.x or 16.x Next.js versions should upgrade to a patched, stable version immediately.

1 The affected React packages are:

  • react-server-dom-parcel
  • react-server-dom-turbopack
  • react-server-dom-webpack

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-59472

A denial of service vulnerability exists in Next.js versions with Partial Prerendering (PPR) enabled when running in minimal mode. The PPR resume endpoint accepts unauthenticated POST requests with the Next-Resume: 1 header and processes attacker-controlled postponed state data. Two closely related vulnerabilities allow an attacker to crash the server process through memory exhaustion:

  1. Unbounded request body buffering: The server buffers the entire POST request body into memory using Buffer.concat() without enforcing any size limit, allowing arbitrarily large payloads to exhaust available memory.

  2. Unbounded decompression (zipbomb): The resume data cache is decompressed using inflateSync() without limiting the decompressed output size. A small compressed payload can expand to hundreds of megabytes or gigabytes, causing memory exhaustion.

Both attack vectors result in a fatal V8 out-of-memory error (FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory) causing the Node.js process to terminate. The zipbomb variant is particularly dangerous as it can bypass reverse proxy request size limits while still causing large memory allocation on the server.

To be affected, an application must run with experimental.ppr: true or cacheComponents: true configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable.

Strongly consider upgrading to 15.6.0-canary.61 or 16.1.5 to reduce risk and prevent availability issues in Next applications.


Release Notes

vercel/next.js (next)

v16.0.0

Compare Source

v15.5.11

Compare Source

v15.5.10

Compare Source

v15.5.9

Compare Source

v15.5.8

Compare Source

v15.5.7

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 08ad7ef to b09925e Compare December 4, 2025 00:33
@renovate renovate bot changed the title Update dependency next to v15.5.7 [SECURITY] Update dependency next to v15.5.7 [SECURITY] - autoclosed Dec 4, 2025
@renovate renovate bot closed this Dec 4, 2025
@renovate renovate bot deleted the renovate/npm-next-vulnerability branch December 4, 2025 20:42
@renovate renovate bot changed the title Update dependency next to v15.5.7 [SECURITY] - autoclosed Update dependency next to v15.5.7 [SECURITY] Dec 5, 2025
@renovate renovate bot reopened this Dec 5, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from b09925e to 587271f Compare December 5, 2025 04:35
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 587271f to a28b46b Compare December 12, 2025 04:37
@renovate renovate bot changed the title Update dependency next to v15.5.7 [SECURITY] Update dependency next to v15.5.8 [SECURITY] Dec 12, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from a28b46b to 99adbee Compare December 21, 2025 07:30
@renovate renovate bot changed the title Update dependency next to v15.5.8 [SECURITY] chore(deps): update dependency next to v15.5.8 [security] Dec 21, 2025
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 99adbee to 6e87116 Compare December 31, 2025 12:32
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 6e87116 to cb05662 Compare January 8, 2026 18:41
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from a572f45 to 2d67fe3 Compare January 23, 2026 19:10
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 2d67fe3 to 49c3ba6 Compare January 28, 2026 19:08
@renovate renovate bot changed the title chore(deps): update dependency next to v15.5.8 [security] chore(deps): update dependency next to v15.5.10 [security] Jan 28, 2026
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 49c3ba6 to 68b45fc Compare January 29, 2026 16:29
@renovate renovate bot changed the title chore(deps): update dependency next to v15.5.10 [security] fix(deps): update dependency next to v16 [security] Jan 29, 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