-
Notifications
You must be signed in to change notification settings - Fork 1
Update dependency next to v14 [SECURITY] #24
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
master
Choose a base branch
from
renovate/npm-next-vulnerability
base: master
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
15cdeb6
to
49f9898
Compare
ada674d
to
880992f
Compare
506c2d9
to
c48d6c9
Compare
996e2f1
to
7ba5082
Compare
75bdbdd
to
1629d97
Compare
6affe3f
to
3ca27b0
Compare
3ca27b0
to
3daeafa
Compare
3daeafa
to
5d9b79b
Compare
5d9b79b
to
4520c0b
Compare
23bcc67
to
a43e161
Compare
a43e161
to
8e77ac1
Compare
3de0325
to
ad19f62
Compare
7c63149
to
fb29816
Compare
a78fd8b
to
e183e9e
Compare
7c3a961
to
7b033b8
Compare
1c95111
to
5d6f1db
Compare
58d9fd0
to
6da652b
Compare
47c51ff
to
db78a38
Compare
5ef226e
to
07def1d
Compare
569b322
to
891f7ba
Compare
91f4d4b
to
78c9b39
Compare
2c6ab1d
to
1093b80
Compare
1093b80
to
c72e82a
Compare
c72e82a
to
e05f527
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:
^8.0.0
->^14.2.32
GitHub Vulnerability Alerts
CVE-2021-43803
Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package
next
hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.CVE-2021-37699
Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when
pages/_error.js
was statically generated, allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.Impact
10.0.5
and10.2.0
11.0.0
and11.0.1
usingpages/_error.js
withoutgetInitialProps
11.0.0
and11.0.1
usingpages/_error.js
andnext export
pages/404.js
next
npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.We recommend upgrading to the latest version of Next.js to improve the overall security of your application.
Patches
https://github.com/vercel/next.js/releases/tag/v11.1.0
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-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
Cookie
orAuthorization
), 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.domains
orimages.remotePatterns
are 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-2020-5284
Impact
serverless
targetnext export
We recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
Patches
https://github.com/zeit/next.js/releases/tag/v9.3.2
References
https://github.com/zeit/next.js/releases/tag/v9.3.2
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.
Release Notes
vercel/next.js (next)
v14.2.32
Compare Source
v14.2.31
Compare Source
Core Changes
Credits
Huge thanks to @styfle and @ztanner for helping!
v14.2.30
Compare Source
v14.2.29
Compare Source
v14.2.28
Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
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
: #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
: #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 this update again.
This PR was generated by Mend Renovate. View the repository job log.