-
Notifications
You must be signed in to change notification settings - Fork 0
Update dependency next to v15 [SECURITY] #350
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.
Open
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
c25c3f9 to
f686046
Compare
f686046 to
9958b47
Compare
9958b47 to
1a3eff0
Compare
1a3eff0 to
c67126a
Compare
c67126a to
a96ba92
Compare
a96ba92 to
910d964
Compare
910d964 to
f7bd7a1
Compare
f7bd7a1 to
2197793
Compare
2197793 to
e22b575
Compare
fe7e455 to
67631d4
Compare
67631d4 to
93ea303
Compare
Contributor
Author
|
93ea303 to
5a49de9
Compare
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:
^14.2.18→^15.0.0^14.2.18→^15.0.0GitHub Vulnerability Alerts
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
GHSA-mwv6-3258-q52c
A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as CVE-2025-55184.
A malicious HTTP request can be crafted and sent to any App Router endpoint that, when deserialized, can cause the server process to hang and consume CPU. This can result in denial of service in unpatched environments.
GHSA-5j59-xgg2-r9c4
It was discovered that the fix for CVE-2025-55184 in React Server Components was incomplete and did not fully mitigate denial-of-service conditions across all payload types. As a result, certain crafted inputs could still trigger excessive resource consumption.
This vulnerability affects React versions 19.0.2, 19.1.3, and 19.2.2, as well as frameworks that bundle or depend on these versions, including Next.js 13.x, 14.x, 15.x, and 16.x when using the App Router. The issue is tracked upstream as CVE-2025-67779.
A malicious actor can send a specially crafted HTTP request to a Server Function endpoint that, when deserialized, causes the React Server Components runtime to enter an infinite loop. This can lead to sustained CPU consumption and cause the affected server process to become unresponsive, resulting in a denial-of-service condition in unpatched environments.
CVE-2025-59471
A DoS vulnerability exists in self-hosted Next.js applications that have
remotePatternsconfigured for the Image Optimizer. The image optimization endpoint (/_next/image) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires thatremotePatternsis configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain.Strongly consider upgrading to 15.5.10 and 16.1.5 to reduce risk and prevent availability issues in Next applications.
GHSA-h25m-26qc-wcjf
A vulnerability affects certain React Server Components packages for versions 19.0.x, 19.1.x, and 19.2.x and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x, and 16.x using the App Router. The issue is tracked upstream as CVE-2026-23864.
A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage, out-of-memory exceptions, or server crashes. This can result in denial of service in unpatched environments.
Release Notes
vercel/next.js (next)
v15.0.8Compare Source
Please see this changelog for more information about this security patch.
v15.0.7Compare Source
v15.0.6Compare Source
v15.0.5Compare Source
Please see CVE-2025-66478 for additional details about this release.
v15.0.4Compare Source
Core Changes
Credits
Huge thanks to @eps1lon
v15.0.3Compare Source
Core Changes
basePathinfindSourceMapURL: #71719pnpm-workspace.yamlto test fixtures to bypass PNPM workspace checks: #7172669d4b800-20241021to45804af1-20241021: #71718--turbopackflag when--turboexists innext dev: #7173045804af1-20241021to28668d39-20241023: #7174528668d39-20241023to1631855f-20241023: #71769turbopack://[project]/...sourcemap uris withfile://...in development: #71489--turboto--turbopackif applicable: #71737"use cache": #71793--enable-source-mapsby default innext dev: #71820registerClientReferencefor ESM client component modules: #71968awaitofparamswhen metadata is used with an image file: #718711631855f-20241023to02c0e824-20241028: #71979ignoreListwhen Webpack is used: #71821next-dynamic-access-named-export: #72016Example Changes
Misc Changes
__turbopack_original__while tree shaking: #71547"use cache"on before code snippet: #71815packages/next/src/compiled: #71986use cache: Add text code formatting: #71999cacheTagFunction Usage: #71912use cachecomments : #71981Credits
Huge thanks to @ytori, @unstubbable, @huozhi, @SebassNoob, @tatsuteb, @Marukome0743, @gnoff, @samcx, @devjiwonchoi, @imprakharshukla, @migueldamota, @eps1lon, @ztanner, @timneutkens, @cantemizyurek, @sebmarkbage, @padmaia, @ijjk, @styfle, @wbinnssmith, @feedthejim, @kdy1, @shuding, @molebox, @ismaelrumzan, @sokra, @bgw, @timeyoutakeit, @AdonisAgelis, @chicoxyzzy, @gaojude, @elitalpa, @t3dotgg, @gaearon, @nisabmohd, @gadcam, @delbaoliveira, @bennettdams, @wiscaksono, and @Developerayo for helping!
v15.0.2Compare Source
Core Changes
basePathinfindSourceMapURL: #71719pnpm-workspace.yamlto test fixtures to bypass PNPM workspace checks: #7172669d4b800-20241021to45804af1-20241021: #71718--turbopackflag when--turboexists innext dev: #7173045804af1-20241021to28668d39-20241023: #7174528668d39-20241023to1631855f-20241023: #71769turbopack://[project]/...sourcemap uris withfile://...in development: #71489--turboto--turbopackif applicable: #71737"use cache": #71793--enable-source-mapsby default innext dev: #71820registerClientReferencefor ESM client component modules: #71968awaitofparamswhen metadata is used with an image file: #718711631855f-20241023to02c0e824-20241028: #71979ignoreListwhen Webpack is used: #71821next-dynamic-access-named-export: #72016Example Changes
Misc Changes
__turbopack_original__while tree shaking: #71547"use cache"on before code snippet: #71815packages/next/src/compiled: #71986use cache: Add text code formatting: #71999cacheTagFunction Usage: #71912use cachecomments : #71981Credits
Huge thanks to @ytori, @unstubbable, @huozhi, @SebassNoob, @tatsuteb, @Marukome0743, @gnoff, @samcx, @devjiwonchoi, @imprakharshukla, @migueldamota, @eps1lon, @ztanner, @timneutkens, @cantemizyurek, @sebmarkbage, @padmaia, @ijjk, @styfle, @wbinnssmith, @feedthejim, @kdy1, @shuding, @molebox, @ismaelrumzan, @sokra, @bgw, @timeyoutakeit, @AdonisAgelis, @chicoxyzzy, @gaojude, @elitalpa, @t3dotgg, @gaearon, @nisabmohd, @gadcam, @delbaoliveira, @bennettdams, @wiscaksono, and @Developerayo for helping!
v15.0.1Compare Source
Core Changes
@next/fontfrom optional Next.js packages to install: #7156365a56d0e-20241020to69d4b800-20241021: #71568endpointfunction indirection: #71572Example Changes
with-supabaseto be compatible with Nextjs 15: #71631Misc Changes
module_resolution: "nodenext"withmjsorcjs: #71635pnpm debug: #71653Credits
Huge thanks to @gnoff, @devjiwonchoi, @samcx, @ztanner, @unstubbable, @huozhi, @mischnic, @lubieowoce, @eps1lon, @ivasilov, @styfle, @bgw, @stipsan, and @timneutkens for helping!
v15.0.0Compare Source
Core Changes
lib/helpers/install.tsto better support pnpm and properly respectrootargument: #64418Metadata.openGraphvalues not resolving basic values whentypeis set: #63620postcsswithuseLightningcss: #64379@appsignal/nodejsto the external packages list: #64503swc_coretov0.90.33: #64553Configuration
📅 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.