Update dependency next to v14.2.30 [SECURITY] #539
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Deploying selfie with
|
| Latest commit: |
658bf3f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b14ebb70.selfie-4ye.pages.dev |
| Branch Preview URL: | https://renovate-npm-next-vulnerabil.selfie-4ye.pages.dev |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
14.2.21->14.2.30GitHub Vulnerability Alerts
CVE-2025-48068
Summary
A low-severity vulnerability in Next.js has been fixed in version 15.2.2. This issue may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while
npm run devis active.Because the mitigation is potentially a breaking change for some development setups, to opt-in to the fix, you must configure
allowedDevOriginsin your next config after upgrading to a patched version. Learn more.Learn more: https://vercel.com/changelog/cve-2025-48068
Credit
Thanks to sapphi-red and Radman Siddiki for responsibly disclosing this issue.
Release Notes
vercel/next.js (next)
v14.2.30Compare Source
v14.2.29Compare Source
v14.2.28Compare Source
v14.2.27Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
v14.2.26Compare Source
Core Changes
v14.2.25Compare Source
Core Changes
Credits
Huge thanks to @ijjk for helping!
v14.2.24Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
v14.2.23Compare Source
Core Changes
Credits
Huge thanks to @styfle, @ijjk and @lubieowoce for helping!
v14.2.22Compare Source
Core Changes
Credits
Huge thanks to @unstubbable, @ijjk, and @ztanner for helping!
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.