Update dependency next to v14.2.10 [SECURITY]#73
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 18, 2024 20:52
5b624d9 to
4944474
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 25, 2025 03:15
4944474 to
95a57c4
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the
Comment |
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 26, 2025 23:51
95a57c4 to
eafdce9
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 16, 2025 03:26
eafdce9 to
1e6b8a4
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
October 23, 2025 07:48
1e6b8a4 to
aec477e
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
November 19, 2025 03:51
cd44b7e to
d79e2ef
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
December 4, 2025 12:05
d79e2ef to
6aa6108
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
January 1, 2026 15:45
6aa6108 to
ecd3ac8
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
January 9, 2026 15:48
ecd3ac8 to
1ee6a64
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
January 20, 2026 02:59
1ee6a64 to
d584ccb
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
February 3, 2026 23:09
d584ccb to
7b060bd
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
February 19, 2026 07:17
a507638 to
b4f68e3
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
2 times, most recently
from
March 14, 2026 15:31
2fca5fe to
358da1b
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 15, 2026 11:55
358da1b to
09e2945
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
April 30, 2026 03:51
09e2945 to
8eaf325
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
May 13, 2026 23:16
8eaf325 to
60c844e
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
May 21, 2026 08:07
60c844e to
a8145ef
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
June 12, 2026 15:37
a8145ef to
5f09240
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
July 16, 2026 00:13
5f09240 to
23f99de
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
July 18, 2026 11:06
23f99de to
7eee3a1
Compare
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
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:
^13.5.6→^14.0.014.0.2→14.2.1013.5.4→14.2.10Next.js Server-Side Request Forgery in Server Actions
CVE-2024-34351 / GHSA-fr5h-rqp8-mj6g
More information
Details
Impact
A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions by security researchers at Assetnote. If the
Hostheader 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
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Next.js Cache Poisoning
CVE-2024-46982 / GHSA-gp8f-8m3g-qvj9
More information
Details
Impact
By sending a crafted HTTP request, it is possible to poison the cache of a non-dynamic server-side rendered route in the pages router (this does not affect the app router). When this crafted request is sent it could coerce Next.js to cache a route that is meant to not be cached and send a
Cache-Control: s-maxage=1, stale-while-revalidateheader which some upstream CDNs may cache as well.To be potentially affected all of the following must apply:
pages/dashboard.tsxnotpages/blog/[slug].tsxThe below configurations are unaffected:
Patches
This vulnerability was resolved in Next.js v13.5.7, v14.2.10, and later. We recommend upgrading regardless of whether you can reproduce the issue or not.
Workarounds
There are no official or recommended workarounds for this issue, we recommend that users patch to a safe version.
Credits
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
vercel/next.js (next)
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: #61426@vercel/nft@0.26.3: #61538next/fontmanifest: #61424@swc/helperstov0.5.5: #61659MiddlewareConfiginterface: #61576.eslintrc.jsonnot being created bynext linton App Router: #5510460a927dto2bc7d33: #61522ReadonlyURLSearchParamsshould extendURLSearchParams: #61419squooshin favor ofsharpas optional dep: #61696MiddlewareConfigwith documentation: #61718exports.foofromcjs_finder: #61795squooshin favor ofsharpas optional dep": #61810useLightningcssforstyled-jsx: #61359remotePatternswith a dot in the pathname: #604882bc7d33toba5e6a8: #61837useLightningcssforstyled-jsx: #61359remotePatternswith a dot in the pathname: #604882bc7d33toba5e6a8: #61837fillandsizes="100vw": #61949swc_coretov0.90.7and update turbopack: #61662Next-URL: #61235@vercel/nft@0.26.4: #62019swc_coretov0.90.8: #61976x-forwarded-protoheaders: #58824react-dom/serverin rsc context: #61165zeromqto server-external-packages.json: #62105turbopack-240215.5: [#621Configuration
📅 Schedule: (UTC)
🚦 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.