Skip to content

Update dependency next to v15.5.10 [SECURITY]#56

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

Update dependency next to v15.5.10 [SECURITY]#56
renovate[bot] wants to merge 1 commit intomasterfrom
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.10 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.


Release Notes

vercel/next.js (next)

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 28, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 217331c to 5663386 Compare February 2, 2026 20:14
@renovate renovate bot changed the title chore(deps): update dependency next to v15.5.10 [security] fix(deps): update dependency next to v16 [security] Feb 2, 2026
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 5663386 to 5a4f67e Compare February 5, 2026 18:42
@renovate renovate bot changed the title fix(deps): update dependency next to v16 [security] chore(deps): update dependency next to v15.5.10 [security] Feb 5, 2026
@renovate renovate bot changed the title chore(deps): update dependency next to v15.5.10 [security] Update dependency next to v15.5.10 [SECURITY] Feb 9, 2026
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 5a4f67e to d3d1f21 Compare February 12, 2026 10:41
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from d3d1f21 to 1c36a43 Compare February 17, 2026 21:07
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