Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 3, 2025

This PR contains the following updates:

Package Change Age Confidence
next (source) 15.2.3 -> 15.2.4 age confidence

GitHub Vulnerability Alerts

CVE-2025-30218

Summary

In the process of remediating CVE-2025-29927, we looked at other possible exploits of Middleware. We independently verified this low severity vulnerability in parallel with two reports from independent researchers.

Learn more here.

Credit

Thank you to Jinseo Kim kjsman and RyotaK (GMO Flatt Security Inc.) with takumi-san.ai for the responsible disclosure. These researchers were awarded as part of our bug bounty program.


Release Notes

vercel/next.js (next)

v15.2.4

Compare Source

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

Core Changes
  • Match subrequest handling for edge and node (#​77474)
  • exclude images and static media from dev origin check (#​77417)
  • ensure /__next middleware URLs are included in the origin check (#​77416)
  • remove direct ip/port bypass in dev origin check (#​77414)
  • switch development origin verification to be opt-in rather than opt-out (#​77395)
Credits

Huge thanks to @​ijjk and @​ztanner for helping!


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 by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Apr 3, 2025

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

Name Status Preview Comments Updated (UTC)
lyonjs-website ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 28, 2025 8:03pm

@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 2eea4bf to bd24b58 Compare April 15, 2025 09:20
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from bd24b58 to aa875e2 Compare April 16, 2025 21:39
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from ea30569 to 35c3bbf Compare April 16, 2025 21:43
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 35c3bbf to 57c0758 Compare April 17, 2025 13:24
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 57c0758 to 387f441 Compare April 17, 2025 14:55
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 387f441 to ab3fb71 Compare April 19, 2025 13:58
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from ab3fb71 to 06cd23c Compare April 24, 2025 06:45
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 06cd23c to 1d4d80e Compare May 27, 2025 11:57
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 1d4d80e to 41db7dd Compare June 3, 2025 22:31
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 41db7dd to 9a41efd Compare July 28, 2025 19:47
@renovate renovate bot force-pushed the renovate/npm-next-vulnerability branch from 9a41efd to f151448 Compare July 28, 2025 19:50
@Slashgear Slashgear merged commit 2a292bb into master Jul 28, 2025
6 of 7 checks passed
@Slashgear Slashgear deleted the renovate/npm-next-vulnerability branch July 28, 2025 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant