fix(deps): update dependency next to v15.4.7 [security] - autoclosed - #1507
Closed
renovate[bot] wants to merge 1 commit into
Closed
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
March 22, 2025 16:13
bdb403a to
6dbfc60
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
August 2, 2025 20:14
6dbfc60 to
ca02053
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
August 19, 2025 19:15
ca02053 to
c06e717
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
August 31, 2025 09:45
c06e717 to
0eea13e
Compare
renovate
Bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
September 27, 2025 00:02
0eea13e to
7ab31f2
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.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot].This notice will be removed on 2025-10-07.
This PR contains the following updates:
15.0.4->15.4.7GitHub Vulnerability Alerts
CVE-2024-56332
Impact
A Denial of Service (DoS) attack allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution.
Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.
Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing.
This is the same issue as if the incoming HTTP request has an invalid
Content-Lengthheader or never closes. If the host has no other mitigations to those then this vulnerability is novel.This vulnerability affects only Next.js deployments using Server Actions.
Patches
This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8. We recommend that users upgrade to a safe version.
Workarounds
There are no official workarounds for this vulnerability.
Credits
Thanks to the PackDraw team for responsibly disclosing this vulnerability.
CVE-2025-29927
Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
15.2.314.2.2513.5.912.3.5Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.
Workaround
If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the
x-middleware-subrequestheader from reaching your Next.js application.Credits
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.
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-49826
Summary
A vulnerability affecting Next.js has been addressed. It impacted versions 15.0.4 through 15.1.8 and involved a cache poisoning bug leading to a Denial of Service (DoS) condition.
Under certain conditions, this issue may allow a HTTP 204 response to be cached for static pages, leading to the 204 response being served to all users attempting to access the page
More details: CVE-2025-49826
Credits
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-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
Release Notes
vercel/next.js (next)
v15.4.7Compare Source
v15.4.6Compare Source
Core Changes
_errorpage'sreq.urlcan be overwritten to dynamic param on minimal mode (#82347)?dplto fonts in/_next/static/media(#82384)Credits
Huge thanks to @devjiwonchoi, @ijjk, and @styfle for helping!
v15.4.5Compare Source
v15.4.4Compare Source
v15.4.3Compare Source
v15.4.2Compare Source
v15.4.1Compare Source
v15.4.0Compare Source
v15.3.5Compare Source
Core Changes
Misc Changes
Credits
Huge thanks to @ztanner, @mischnic, and @bgw for helping!
v15.3.4Compare Source
Core Changes
Credits
Huge thanks to @huozhi for helping!
v15.3.3Compare Source
Core Changes
vary(#79939)Credits
Huge thanks to @gaojude, @kdy1, @bgw, and @unstubbable for helping!
v15.3.2Compare Source
Core Changes
Credits
Huge thanks to @ijjk, @huozhi, @kdy1, @wbinnssmith, and @bgw for helping!
v15.3.1Compare Source
Core Changes
Credits
Huge thanks to @kdy1 and @styfle for helping!
v15.3.0Compare Source
Core Changes
<select>styling for consistency: #76973029e8bd6-20250306to0ca3deeb-20250311: #769890ca3deeb-20250311to6aa8254b-20250312: #77033sizesetting to preferences: #77027'seconds'cache life profile: #77084next info: #770596aa8254b-20250312to5398b711-20250314: #77129useLightningcssoption tostyled-jsxcorrectly: #77008useErrorOverlayReducer: #77205revalidate*: #76885revalidate*work when followed by a redirect in a route handler: #770905398b711-20250314toc69a5fc5-20250318: #77249"use cache"caches when Draft Mode is enabled: #77141c69a5fc5-20250318todb7dfe05-20250319: #77295db7dfe05-20250319to740a4f7a-20250325: #77507740a4f7a-20250325to313332d1-20250326: #77527expireTags/getExpirationunnecessarily: #77570NEXT_PRIVATE_DEBUG_CACHEenv variable for cache handler debug logs: #77585nodejsruntime in middleware: #77553"use cache"revalidation logic out of incremental cache: #77577313332d1-20250326to63779030-20250328: #77643isrFlushToDiskoption to prevent writing optimized images to cache: #70645nodejsruntime in middleware": #77690new URL()forimages.remotePatterns: #7769263779030-20250328to040f8286-20250402: #77742useLayoutEffectwarning if React 18 is used: #77737next start: #77714TurbopackInternalErrors occur: #77660sideEffectsmatching for non-relative globs: #77693issueCountfrom non-asyncerrorsarray: #77821refreshTagsandgetExpiration: #77779"use cache"wrapper: #77827searchParamsaccess in"use cache"triggers error when caught: #77838getSourceFileinstead offileExiststo check file existence: #77863040f8286-20250402to33661467-20250407: #77899next/*entrypoints: #77844Example Changes
canaryversion: #77754Misc Changes
charset=utf-8in data-url source maps: #77112react-refreshas a dependency of plugin: #77142swc_coretov16.6.0: #77155swc_coretov16.6.2: #77194.minify()of lightningcssStyleSheet: #77313swc_coreand userayoninstead ofchili: #77338copy_dirconcurrency to avoid running out of file descriptors: #77468swc_coretov16.10.0: #77489launch.jsonto improve debugging in VSCode: #76559bunand other package manager: #77633--js-buildas option instead of--no-js-build: #77686Metadata and OG imagespage: #74077Upgradepage: #77717ExamplestoGuides: #77722swc_coretov19.0.0: #77669Vcin a struct: #77756instrumentation-clientfollow up: #77752styled-components: #77736use serverand update examples: #77770use serverand update examples": #77771hygieneif mangling is disabled: #77815Configuration
📅 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.