10BC0 🚨 [security] Update all of nextjs 16.1.0 → 16.1.5 (patch) by depfu[bot] · Pull Request #19603 · tailwindlabs/tailwindcss · GitHub
[go: up one dir, main page]
Skip to content

🚨 [security] Update all of nextjs 16.1.0 → 16.1.5 (patch) #19603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
depfu wants to merge 1 commit into from
Closed

🚨 [security] Update all of nextjs 16.1.0 → 16.1.5 (patch) #19603

depfu wants to merge 1 commit into from
+82 −76

Conversation

@depfu
Copy link
Contributor
@depfu depfu bot commented Jan 27, 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 update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint-config-next (16.1.0 → 16.1.5)

Sorry, we couldn't find anything useful about this release.

✳️ next (16.1.0 → 16.1.5) · Repo

Security Advisories 🚨

🚨 Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration

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

16.1.5

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472
https://vercel.com/changelog/summary-of-cve-2026-23864

16.1.4

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Only filter next config if experimental flag is enabled (#88733)

Credits

Huge thanks to @mischnic for helping!

16.1.3

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Fix linked list bug in LRU deleteFromLru (#88652)
  • Fix relative same host redirects in node middleware (#88253)

Credits

Huge thanks to @acdlite and @ijjk for helping!

16.1.2

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Turbopack: Update to swc_core v50.2.3 (#87841) (#88296)
    • Fixes a crash when processing mdx files with multibyte characters. (#87713)
  • Turbopack: mimalloc upgrade and enabling it on musl (#88503) (#87815) (#88426)
    • Fixes a significant performance issue on musl-based Linux distributions (e.g. Alpine in Docker) related to musl's allocator.
    • Other platforms have always used mimalloc, but we previously did not use mimalloc on musl because of compilation issues that have since been resolved.

Credits

Huge thanks to @mischnic for helping!

16.1.1

Note

This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Turbopack: Create junction points instead of symlinks on Windows (#87606)

Credits

Huge thanks to @sokra 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 20 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 January 27, 2026 20:07
@depfu depfu bot added the depfu label Jan 27, 2026
@coderabbitai
Copy link
coderabbitai bot commented Jan 27, 2026

Walkthrough

This pull request updates dependency versions in two Next.js playground package configuration files. Specifically, the next package is bumped from version ^16.1.0 to ^16.1.5, and eslint-config-next is updated from ^16.1.0 to ^16.1.5. These changes are applied to both the playgrounds/nextjs/package.json and playgrounds/v3/package.json files, with version updates appearing in both the dependencies and devDependencies sections. No modifications to functional logic or configuration behavior are introduced.

🚥 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 Next.js from version 16.1.0 to 16.1.5 as a security patch across all playgrounds.
Description check ✅ Passed The description is directly related to the changeset, providing detailed information about the security vulnerabilities being fixed, release notes, and commit history for the Next.js 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.

@RobinMalfait RobinMalfait mentioned this pull request Jan 28, 2026
Open
@depfu
Copy link
Contributor Author
depfu bot commented Jan 28, 2026

Closed in favor of #19609.

@depfu depfu bot closed this Jan 28, 2026
@depfu depfu bot deleted the depfu/update/pnpm/group/nextjs-16.1.5 branch January 28, 2026 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants

0