fix(deps): update dependency next to v14.2.32 [security] #2025
+47 −47
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
| Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Note Free review on us!CodeRabbit is offering free reviews until Thu Nov 06 2025 to showcase some of the refinements we've made. Comment |
❌ Deploy Preview for kleros-v2-university failed. Why did it fail? →
|
❌ Deploy Preview for kleros-v2-testnet-devtools failed. Why did it fail? →
|
✅ Deploy Preview for kleros-v2-neo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for kleros-v2-testnet ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
renovate bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from ba9f754 to cca90ad Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 0260213 to 2d540bc Compare 
| Code Climate has analyzed commit 2d540bc and detected 0 issues on this pull request. View more on Code Climate. |
renovate bot force-pushed the renovate/npm-next-vulnerability branch 11 times, most recently from 533d821 to 20c96a7 Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch 4 times, most recently from b64413d to db7672f Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from cc89579 to 0dc6214 Compare renovate bot changed the title renovate bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from 48b0687 to 1466dce Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch 3 times, most recently from 479cfec to 78fffa7 Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch 5 times, most recently from 9c4848b to 7e401ce Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch 6 times, most recently from 1ecfae8 to 6b1cf39 Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch 5 times, most recently from e9db561 to 606bf0b Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from f7b5425 to 4e06492 Compare renovate bot force-pushed the renovate/npm-next-vulnerability branch from 4e06492 to 2641fd3 Compare 
|
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.28->14.2.32GitHub 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.
CVE-2025-57752
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as
CookieorAuthorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.
More details at Vercel Changelog
CVE-2025-55173
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.
All users relying on
images.domainsorimages.remotePatternsare encouraged to upgrade and verify that external image sources are strictly validated.More details at Vercel Changelog
CVE-2025-57822
A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into
NextResponse.next(). In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the
next()function.More details at Vercel Changelog
Release Notes
vercel/next.js (next)
v14.2.32Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
v14.2.31Compare Source
Core Changes
Credits
Huge thanks to @styfle and @ztanner for helping!
v14.2.30Compare Source
Core Changes
config.allowedDevOrigins(#80410) (Learn More)Credits
Huge thanks to @ijjk and @ztanner for helping!
v14.2.29Compare Source
Core Changes
Credits
Huge thanks to @ijjk 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.
PR-Codex overview
This PR updates the version of
nextand its related packages from14.2.28to14.2.32in bothpackage.jsonandyarn.lock, ensuring compatibility with the latest features and fixes.Detailed summary
nextversion from14.2.28to14.2.32inpackage.json.nextversion from14.2.28to14.2.32inyarn.lock.@next/env,@next/swc-*packages to14.2.32inyarn.lock.nextinyarn.lock.