Skip to content

🚨 [security] Update next 16.2.2 β†’ 16.2.3 (patch)#19922

Open
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/next-16.2.3
Open

🚨 [security] Update next 16.2.2 β†’ 16.2.3 (patch)#19922
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/next-16.2.3

Conversation

@depfu
Copy link
Copy Markdown
Contributor

@depfu depfu bot commented Apr 10, 2026


🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!


Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ next (16.2.2 β†’ 16.2.3) Β· Repo

Security Advisories 🚨

🚨 Next.js has a Denial of Service with Server Components

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.

Release Notes

16.2.3

Note

This release is backporting security and bug fixes. For more information about the fixed security vulnerability, please see https://vercel.com/changelog/summary-of-cve-2026-23869. The release does not include all pending features/changes on canary.

Core Changes

  • Ensure app-page reports stale ISR revalidation errors via onRequestError (#92282)
  • Fix [Bug]: manifest.ts breaks HMR in Next.js 16.2 (#91981 through #92273)
  • Deduplicate output assets and detect content conflicts on emit (#92292)
  • Fix styled-jsx race condition: styles lost due to concurrent rendering (#92459)
  • turbo-tasks-backend: stability fixes for task cancellation and error handling (#92254)

Credits

Huge thanks to @icyJoseph, @sokra, @wbinnssmith, @eps1lon and @ztanner for helping!

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 9 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot requested a review from a team as a code owner April 10, 2026 16:07
@depfu depfu bot added the depfu label Apr 10, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 10, 2026

No actionable comments were generated in the recent review. πŸŽ‰

ℹ️ Recent review info
βš™οΈ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 8a3e8092-0a2a-4cb8-91c9-1bb40efe9beb

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between aad6017 and 0bccf1e.

β›” Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
πŸ“’ Files selected for processing (2)
  • playgrounds/nextjs/package.json
  • playgrounds/v3/package.json

Walkthrough

The next dependency version was updated in two package configuration files. The playgrounds/nextjs/package.json file was modified to change the next version from 16.2.2 to 16.2.3. Similarly, the playgrounds/v3/package.json file was updated with the same version change for the next dependency. No other dependencies, scripts, or configuration values were altered in these files.

πŸš₯ Pre-merge checks | βœ… 2
βœ… Passed checks (2 passed)
Check name Status Explanation
Title check βœ… Passed The title clearly and specifically describes the main change: updating the Next.js dependency from 16.2.2 to 16.2.3 to address security vulnerabilities.
Description check βœ… Passed The description is directly related to the changeset, providing detailed information about the security vulnerability (CVE-2026-23869), release notes, and changes included in the patch version update.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

@depfu
Copy link
Copy Markdown
Contributor Author

depfu bot commented Apr 10, 2026

Sorry, but the merge failed with:

At least 1 approving review is required by reviewers with write access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants