Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

fix(deps): update dependency next to v15.2.3 [security]#520

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.

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

Already on GitHub?Sign in to your account

Merged
Slashgear merged 1 commit intomasterfromrenovate/npm-next-vulnerability
Mar 25, 2025

Conversation

@renovate
Copy link
Contributor

@renovaterenovatebot commentedMar 21, 2025
edited
Loading

This PR contains the following updates:

PackageChangeAgeAdoptionPassingConfidence
next (source)15.2.2 ->15.2.3ageadoptionpassingconfidence

GitHub Vulnerability Alerts

CVE-2025-29927

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 in15.2.3
  • For Next.js 14.x, this issue is fixed in14.2.25
  • For Next.js 13.x, this issue is fixed in13.5.9
  • For Next.js 12.x, this issue is fixed in12.3.5
  • For Next.js 11.x, consult the below workaround.

Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.

Workaround

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

Credits

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

Release Notes

vercel/next.js (next)

v15.2.3

Compare Source


Configuration

📅Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦Automerge: Enabled.

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 this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated byMend Renovate. View therepository job log.

@vercel
Copy link

vercelbot commentedMar 21, 2025
edited
Loading

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

NameStatusPreviewCommentsUpdated (UTC)
lyonjs-website✅ Ready (Inspect)Visit Preview💬Add feedbackMar 24, 2025 11:42pm

@renovaterenovatebot changed the titlefix(deps): update dependency next to v15.2.3 [security]fix(deps): update dependency next to v15.2.3 [security] - autoclosedMar 24, 2025
@renovaterenovatebot closed thisMar 24, 2025
@renovaterenovatebot deleted the renovate/npm-next-vulnerability branchMarch 24, 2025 16:30
@renovaterenovatebot changed the titlefix(deps): update dependency next to v15.2.3 [security] - autoclosedfix(deps): update dependency next to v15.2.3 [security]Mar 24, 2025
@renovaterenovatebot reopened thisMar 24, 2025
@renovaterenovatebotforce-pushed therenovate/npm-next-vulnerability branch from5935d75 to24bf7bdCompareMarch 24, 2025 23:41
@SlashgearSlashgear merged commit2890ac9 intomasterMar 25, 2025
9 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Slashgear

[8]ページ先頭

©2009-2025 Movatter.jp