-
Notifications
You must be signed in to change notification settings - Fork 0
Update dependency next to v14 [SECURITY] #10
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
base: main
Are you sure you want to change the base?
Conversation
|
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
bb4c13c
to
7f4cb28
Compare
7f4cb28
to
5b9d0e0
Compare
5b9d0e0
to
1fa8f44
Compare
1fa8f44
to
f48f25c
Compare
f48f25c
to
ffba37d
Compare
ffba37d
to
acf1121
Compare
acf1121
to
e5bef4b
Compare
e5bef4b
to
4a1d69a
Compare
4a1d69a
to
0060e2a
Compare
0060e2a
to
63390aa
Compare
63390aa
to
65d408f
Compare
65d408f
to
2f83404
Compare
2f83404
to
38a7969
Compare
e5e2f99
to
2b5bcd6
Compare
2b5bcd6
to
9c381a4
Compare
9c381a4
to
5a06c3a
Compare
5a06c3a
to
905a89b
Compare
905a89b
to
95f0c90
Compare
95f0c90
to
fa6f36c
Compare
fa6f36c
to
54e494b
Compare
54e494b
to
9e49fae
Compare
9e49fae
to
36d6e3d
Compare
36d6e3d
to
6f13bed
Compare
This PR contains the following updates:
^13.4.12
->^14.2.30
GitHub Vulnerability Alerts
CVE-2024-34351
Impact
A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions by security researchers at Assetnote. If the
Host
header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself.Prerequisites
<14.1.1
) is running in a self-hosted* manner./
.* Many hosting providers (including Vercel) route requests based on the Host header, so we do not believe that this vulnerability affects any Next.js applications where routing is done in this manner.
Patches
This vulnerability was patched in #62561 and fixed in Next.js
14.1.1
.Workarounds
There are no official workarounds for this vulnerability. We recommend upgrading to Next.js
14.1.1
.Credit
Vercel and the Next.js team thank Assetnote for responsibly disclosing this issue to us, and for working with us to verify the fix. Thanks to:
Adam Kues - Assetnote
Shubham Shah - Assetnote
CVE-2024-47831
Impact
The image optimization feature of Next.js contained a vulnerability which allowed for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption.
Not affected:
next.config.js
file is configured withimages.unoptimized
set totrue
orimages.loader
set to a non-default value.Patches
This issue was fully patched in Next.js
14.2.7
. We recommend that users upgrade to at least this version.Workarounds
Ensure that the
next.config.js
file has eitherimages.unoptimized
,images.loader
orimages.loaderFile
assigned.Credits
Brandon Dahler (brandondahler), AWS
Dimitrios Vlastaras
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.15
and 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-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
pageProps
data 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.
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 dev
is active.Because the mitigation is potentially a breaking change for some development setups, to opt-in to the fix, you must configure
allowedDevOrigins
in 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.30
Compare Source
v14.2.29
Compare Source
v14.2.28
Compare Source
v14.2.27
Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
v14.2.26
Compare Source
Core Changes
v14.2.25
Compare Source
Core Changes
Credits
Huge thanks to @ijjk for helping!
v14.2.24
Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
v14.2.23
Compare Source
Core Changes
Credits
Huge thanks to @styfle, @ijjk and @lubieowoce for helping!
v14.2.22
Compare Source
Core Changes
Credits
Huge thanks to @unstubbable, @ijjk, and @ztanner for helping!
v14.2.21
Compare Source
Core Changes
14898b6
to178c267
: https://github.com/vercel/next.js/pull/74115Misc Changes
Credits
Huge thanks to @unstubbable, @ztanner, and @styfle for helping!
v14.2.20
Compare Source
Core Changes
Credits
Huge thanks to @wyattjoh for helping!
v14.2.19
Compare Source
Core Changes
Misc Changes
Credits
Huge thanks to @ztanner and @ijjk for helping!
v14.2.18
Compare Source
Core Changes
Credits
Huge thanks to @huozhi and @ijjk for helping!
v14.2.17
Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @ztanner, and @ijjk for helping!
v14.2.16
Compare Source
v14.2.15
Compare Source
Core Changes
Credits
Huge thanks to @ztanner, @agadzik, @huozhi, @styfle, @icyJoseph and @wyattjoh for helping!
v14.2.14
Compare Source
Core Changes
Credits
Huge thanks to @styfle, @ztanner, @ijjk, @huozhi and @wyattjoh for helping!
v14.2.13
Compare Source
Core Changes
Credits
Huge thanks to @raeyoung-kim, @huozhi, @devjiwonchoi, and @ijjk for helping!
v14.2.12
Compare Source
Core Changes
Credits
Huge thanks to @alvarlagerlof, @wyattjoh, @delbaoliveira, and @ijjk for helping!
v14.2.11
Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @devjiwonchoi, and @ijjk for helping!
v14.2.10
Compare Source
Core Changes
Credits
Huge thanks to @huozhi and @ijjk for helping!
v14.2.9
Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @ztanner, @ijjk, and @lubieowoce for helping!
v14.2.8
Compare Source
What's Changed
Support
esmExternals
in 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/image
fixesServer actions improvements
Other changes
Create-next-app updates
create-next-app
template CSS (#66043)create-next-app
public/ 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.7
Compare Source
Core Changes
Credits
Huge thanks to @kjugi, @huozhi, @ztanner, @SukkaW, @marlier, @Kikobeats, @syi0808, @ijjk, and @samcx for helping!
v14.2.6
Compare Source
Core Changes
v14.2.5
Compare Source
Core Changes
Misc
Credits
Huge thanks to @devjiwonchoi, @ijjk, @emmerich, @huozhi, @kdy1, @kwonoj, @styfle, and @sokra for helping!
v14.2.4
Compare Source
Core Changes
Credits
Huge thanks to @ztanner, @ijjk, @wbinnssmith, @huozhi, and @lubieowoce for helping!
v14.2.3
Compare Source
Core Changes
Credits
Huge thanks to @huozhi, @samcx, @ztanner, @Jeffrey-Zutt, and @ijjk for helping!
v14.2.2
Compare 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.1
Compare Source
Core Changes
Credits
Huge thanks to @sokra for helping!
v14.2.0
Compare Source
Learn more: https://nextjs.org/blog/next-14-2
Core Changes
next info
output: #60376terser
tov5.27.0
: #61068swc_core
tov0.87.28
: #60876unoptimized
prop: #61045_app
: #60789optimizeServerReact
to config-shared: #61106maxDuration
to typescript plugin allowed exports: #59193swc_core
tov0.89.x
: #61086swc_core
tov0.89.4
: #61285preset-env
mode ofstyled-jsx
in webpack mode: #61306.ts
files as.tsx
: #61219swc_core
tov0.89.6
: #61426@vercel/nft@0.26.3
: #61538next/font
manifest: #61424@swc/helpers
tov0.5.5
: #61659MiddlewareConfig
interface: #61576.eslintrc.json
not being created bynext lint
on App Router: #5510460a927d
to2bc7d33
: #61522Configuration
📅 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.