generated from 2nthony/empty-starter
-
-
Notifications
You must be signed in to change notification settings - Fork 5
chore(deps): update dependency next to v14 [security] #92
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-next-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
3e8cef5 to
8f569b9
Compare
8f569b9 to
2888d14
Compare
2888d14 to
c0c6194
Compare
c0c6194 to
8cffc55
Compare
8cffc55 to
21538dc
Compare
21538dc to
c6dd86c
Compare
c6dd86c to
9fd9fe1
Compare
9fd9fe1 to
0c7bdf8
Compare
0c7bdf8 to
d0e2eb5
Compare
d0e2eb5 to
13f1b76
Compare
13f1b76 to
4457da1
Compare
4457da1 to
9a20f2c
Compare
9a20f2c to
e440dd4
Compare
ce51e75 to
793191c
Compare
793191c to
64cfe86
Compare
64cfe86 to
21b892d
Compare
21b892d to
b785f50
Compare
b785f50 to
6927b4e
Compare
6927b4e to
15ed186
Compare
15ed186 to
788181c
Compare
788181c to
fc8b74a
Compare
fc8b74a to
63ce7e4
Compare
24d5a79 to
8dd6476
Compare
8dd6476 to
0982376
Compare
0982376 to
2f9bc2e
Compare
2f9bc2e to
4c33b58
Compare
4c33b58 to
a516ebf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
^12.1.0->^14.2.32^13.0.0->^14.0.0GitHub Vulnerability Alerts
CVE-2023-46298
Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN. Cloudflare considers these requests cacheable assets.
CVE-2024-51479
Impact
If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed.
Patches
This issue was patched in Next.js
14.2.15and later.If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version.
Workarounds
There are no official workarounds for this vulnerability.
Credits
We'd like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.
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
CVE-2025-32421
Summary
We received a responsible disclosure from Allam Rachid (zhero) for a low-severity race-condition vulnerability in Next.js. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve
pagePropsdata instead of standard HTML.Learn more here
Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.
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!
v14.2.28Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
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!
v14.2.21Compare Source
Core Changes
14898b6to178c267: #74115Misc Changes
Credits
Huge thanks to @unstubbable, @ztanner, and @styfle for helping!
v14.2.20Compare Source
Core Changes
Credits
Huge thanks to @wyattjoh for helping!
v14.2.19Compare Source
Core Changes
Misc Changes
Credits
Huge thanks to @ztanner and @ijjk for helping!
v14.2.18Compare Source
Core Changes
Credits
Huge thanks to @huozhi and @ijjk for helping!
v14.2.17Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @ztanner, and @ijjk for helping!
v14.2.16Compare Source
v14.2.15Compare Source
Core Changes
Credits
Huge thanks to @ztanner, @agadzik, @huozhi, @styfle, @icyJoseph and @wyattjoh for helping!
v14.2.14Compare Source
Core Changes
Credits
Huge thanks to @styfle, @ztanner, @ijjk, @huozhi and @wyattjoh for helping!
v14.2.13Compare Source
Core Changes
Credits
Huge thanks to @raeyoung-kim, @huozhi, @devjiwonchoi, and @ijjk for helping!
v14.2.12Compare Source
Core Changes
Credits
Huge thanks to @alvarlagerlof, @wyattjoh, @delbaoliveira, and @ijjk for helping!
v14.2.11Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @devjiwonchoi, and @ijjk for helping!
v14.2.10Compare Source
Core Changes
Credits
Huge thanks to @huozhi and @ijjk for helping!
v14.2.9Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @ztanner, @ijjk, and @lubieowoce for helping!
v14.2.8Compare Source
What's Changed
Support
esmExternalsin app directoryReading cookies set in middleware in components and actions
Metadata and icons
fb:app_id,fb:admins) in generateMetaData (#65713)Parallel routes fixes
Draft mode and edge improvements
next/imagefixesServer actions improvements
Other changes
Create-next-app updates
create-next-apptemplate CSS (#66043)create-next-apppublic/ assets from local folder→ remote URL (#66931)Full Changelog: vercel/next.js@v14.2.7...v14.2.8
Huge thanks to everyone who contributed to this release:
@abhi12299, @delbaoliveira, @eps1lon, @ForsakenHarmony, @huozhi, @ijjk, @JoshuaKGoldberg, @leerob, @lubieowoce, @Netail, @ronanru, @samcx, @shuding, @sokra, @stylessh, @timfuhrmann, @wbinnssmith, @wyattjoh, @ypessoa, @ztanner
v14.2.7Compare Source
Core Changes
Credits
Huge thanks to @kjugi, @huozhi, @ztanner, @SukkaW, @marlier, @Kikobeats, @syi0808, @ijjk, and @samcx for helping!
v14.2.6Compare Source
Core Changes
v14.2.5Compare Source
Core Changes
Misc
Credits
Huge thanks to @devjiwonchoi, @ijjk, @emmerich, @huozhi, @kdy1, @kwonoj, @styfle, and @sokra for helping!
v14.2.4Compare Source
Core Changes
Credits
Huge thanks to @ztanner, @ijjk, @wbinnssmith, @huozhi, and @lubieowoce for helping!
v14.2.3Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @samcx, @ztanner, @Jeffrey-Zutt, and @ijjk for helping!
v14.2.2Compare Source
Core Changes
Credits
Huge thanks to @shuding, @coltonehrman, @ztanner, @huozhi, @sokra, @Jeffrey-Zutt, @timneutkens, @wbinnssmith, @wiesson, @ijjk, @devjiwonchoi, and @bgw for helping!
v14.2.1Compare Source
Core Changes
Credits
Huge thanks to @sokra for helping!
v14.2.0Compare Source
Learn more: https://nextjs.org/blog/next-14-2
Core Changes
next infooutput: #60376tersertov5.27.0: #61068swc_coretov0.87.28: #60876unoptimizedprop: #61045_app: #60789optimizeServerReactto config-shared: #61106maxDurationto typescript plugin allowed exports: #59193swc_coretov0.89.x: #61086swc_coretov0.89.4: #61285preset-envmode ofstyled-jsxin webpack mode: #61306.tsfiles as.tsx: #61219swc_coretov0.89.6: #61426Configuration
📅 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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.