Skip to content

🚨 [security] Update next 14.2.23 → 14.2.25 (patch)#319

Closed
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/next-14.2.25
Closed

🚨 [security] Update next 14.2.23 → 14.2.25 (patch)#319
depfu[bot] wants to merge 1 commit intomainfrom
depfu/update/pnpm/next-14.2.25

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented Mar 21, 2025


🚨 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?

✳️ next (14.2.23 → 14.2.25) · Repo

Security Advisories 🚨

🚨 Authorization Bypass in Next.js Middleware

Impact

It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.

Patches

  • For Next.js 15.x, this issue is fixed in 15.2.3
  • For Next.js 14.x, this issue is fixed in 14.2.25
  • For Next.js versions 11.1.4 thru 13.5.6, consult the below workaround.

Workaround

If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application.

Credits

  • Allam Rachid (zhero;)
  • Allam Yasser (inzo_)
Release Notes

14.2.25

Note

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

Core Changes

  • Update middleware request header (#77202)

Credits

Huge thanks to @ijjk for helping!

14.2.24

Note

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

Core Changes

  • fix: ensure lint worker errors aren't silenced (#75779)
  • add additional x-middleware-set-cookie filtering (#75561 & #73482)

Credits

Huge thanks to @ztanner for helping!

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

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


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 added the depfu label Mar 21, 2025
@vercel
Copy link

vercel bot commented Mar 21, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
ts-nextjs-tailwind-starter ✅ Ready (Inspect) Visit Preview Mar 21, 2025 4:59pm

@depfu
Copy link
Contributor Author

depfu bot commented May 15, 2025

Closed in favor of #322.

@depfu depfu bot closed this May 15, 2025
@depfu depfu bot deleted the depfu/update/pnpm/next-14.2.25 branch May 15, 2025 16:27
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