Skip to content

chore(deps): dsw-000 update dependency next to v15.5.10 [security]#293

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

chore(deps): dsw-000 update dependency next to v15.5.10 [security]#293
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-next-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jun 2, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next (source) 15.5.715.5.10 age adoption passing confidence
next (source) 14.2.3315.5.10 age adoption passing 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-5j59-xgg2-r9c4

It was discovered that the fix for CVE-2025-55184 in React Server Components was incomplete and did not fully mitigate denial-of-service conditions across all payload types. As a result, certain crafted inputs could still trigger excessive resource consumption.

This vulnerability affects React versions 19.0.2, 19.1.3, and 19.2.2, as well as frameworks that bundle or depend on these versions, including Next.js 13.x, 14.x, 15.x, and 16.x when using the App Router. The issue is tracked upstream as CVE-2025-67779.

A malicious actor can send a specially crafted HTTP request to a Server Function endpoint that, when deserialized, causes the React Server Components runtime to enter an infinite loop. This can lead to sustained CPU consumption and cause the affected server process to become unresponsive, resulting in a denial-of-service condition 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.


Release Notes

vercel/next.js (next)

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 90c5524 to 5cff1c8 Compare June 6, 2025 13:25
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 5cff1c8 to 398798f Compare June 13, 2025 15:54
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next to v15 [security] chore(deps): dsw-000 update dependency next to v14.2.25 [security] Jun 13, 2025
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 398798f to 7267706 Compare June 15, 2025 04:41
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next to v14.2.25 [security] chore(deps): dsw-000 update dependency next to v14.2.30 [security] Jun 15, 2025
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 7267706 to e9a0c56 Compare July 23, 2025 12:09
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from ed183b3 to f5dd535 Compare August 15, 2025 07:55
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 1737504 to f5321d2 Compare August 26, 2025 14:52
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from f5321d2 to 06a2eea Compare August 31, 2025 23:21
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next to v14.2.30 [security] chore(deps): dsw-000 update dependency next to v14.2.32 [security] Aug 31, 2025
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 06a2eea to aeec28b Compare September 11, 2025 20:07
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next to v14.2.32 [security] chore(deps): dsw-000 update dependency next to v14.2.31 [security] Sep 11, 2025
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from aeec28b to 6b6e499 Compare September 12, 2025 16:52
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next to v14.2.31 [security] chore(deps): dsw-000 update dependency next to v14.2.32 [security] Sep 12, 2025
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch 7 times, most recently from bbbf66a to 0dadcfb Compare September 30, 2025 14:49
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch 6 times, most recently from 3aca522 to b9246b1 Compare October 7, 2025 16:09
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from b9246b1 to d0649c0 Compare October 9, 2025 10:51
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from d0649c0 to a5e7319 Compare October 15, 2025 12:02
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from a5e7319 to d1e6d60 Compare November 6, 2025 12:46
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from fea1ead to 047365a Compare November 20, 2025 17:22
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 047365a to 10a31ce Compare December 3, 2025 19:59
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next to v14.2.32 [security] chore(deps): dsw-000 update dependency next [security] Dec 3, 2025
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next [security] chore(deps): dsw-000 update dependency next [security] - autoclosed Dec 5, 2025
@renovate renovate Bot closed this Dec 5, 2025
@renovate renovate Bot deleted the renovate/npm-next-vulnerability branch December 5, 2025 14:21
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next [security] - autoclosed chore(deps): dsw-000 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 4 times, most recently from b14ea51 to 1aa4f3e Compare December 13, 2025 14:34
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next to v15.5.8 [security] chore(deps): dsw-000 update dependency next [security] Dec 13, 2025
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 1aa4f3e to 1c0ea35 Compare December 14, 2025 06:28
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 1c0ea35 to 26f9339 Compare January 21, 2026 12:05
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 26f9339 to f7f1a43 Compare February 2, 2026 18:37
@renovate renovate Bot force-pushed the renovate/npm-next-vulnerability branch from f7f1a43 to 94c5485 Compare February 5, 2026 17:46
@renovate renovate Bot changed the title chore(deps): dsw-000 update dependency next [security] chore(deps): dsw-000 update dependency next to v15.5.10 [security] Feb 5, 2026
@raoufswe raoufswe closed this Feb 6, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Feb 6, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 15.x releases. But if you manually upgrade to 15.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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