Bump next to 16.2.5 [SECURITY] - autoclosed - #4585
Closed
renovate[bot] wants to merge 1 commit into
Closed
Conversation
renovate
Bot
requested review from
flaviendelangle and
michaldudak
as code owners
April 11, 2026 05:41
commit: |
Bundle size
PerformanceTotal duration: 1,213.10 ms +110.20 ms(+10.0%) | Renders: 50 (+0) | Paint: 1,859.13 ms +197.28 ms(+11.9%)
Check out the code infra dashboard for more information about this PR. |
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 16, 2026 07:56
3ed194e to
b39699b
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 17, 2026 10:43
b39699b to
4d58e11
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 21, 2026 12:43
4d58e11 to
5d69445
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 23, 2026 18:25
5d69445 to
ff33999
Compare
Member
|
Wait to see how Base UI solves it: #4585 |
Member
|
Blocked due to vercel/next.js#91735 (same as #4394) |
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 27, 2026 08:09
ff33999 to
a989132
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 27, 2026 08:15
a989132 to
95616d5
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 27, 2026 08:28
95616d5 to
21ffaa6
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
April 28, 2026 04:25
21ffaa6 to
15e1808
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 28, 2026 20:35
15e1808 to
bcdf98b
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 29, 2026 10:24
bcdf98b to
de3da3a
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
May 11, 2026 14:32
de3da3a to
0377695
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
May 11, 2026 15:09
0377695 to
2a7e8a0
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
16.1.7→16.2.5Next.js has a Denial of Service with Server Components
GHSA-q4gf-8mx6-v5v3
More information
Details
A vulnerability affects certain React Server Components packages for versions 19.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-23869. You can read more about this advisory our this changelog.
A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage. This can result in denial of service in unpatched environments.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js Vulnerable to Denial of Service with Server Components
GHSA-8h8q-6873-q5fj
More information
Details
A vulnerability affects certain React Server Components packages for versions 19.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-23870.
A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage. This can result in denial of service in unpatched environments.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
vercel/next.js (next)
v16.2.5Compare Source
v16.2.4Compare Source
v16.2.3Compare Source
v16.2.2Compare Source
v16.2.1Compare Source
v16.2.0Compare Source
Configuration
📅 Schedule: (in timezone UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.