You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Review the following alerts detected in dependencies.
According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.
Action
Severity
Alert (click "▶" to expand/collapse)
Block
Critical CVE: Authorization Bypass in Next.js Middleware
Next steps: Take a moment to review the security alert
above. Review the linked package source code to understand the potential
risk. Ensure the package is not malicious before proceeding. If you're
unsure how to proceed, reach out to your security team or ask the Socket
team for help at support@socket.dev.
Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/next@15.0.8. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
Warn
Telemetry collection: npm next
Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information
Next steps: Take a moment to review the security alert
above. Review the linked package source code to understand the potential
risk. Ensure the package is not malicious before proceeding. If you're
unsure how to proceed, reach out to your security team or ask the Socket
team for help at support@socket.dev.
Suggestion: Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.
Mark the package as acceptable risk. To ignore this alert only
in this pull request, reply with the comment
@SocketSecurity ignore npm/next@15.0.8. You can
also ignore all packages with @SocketSecurity ignore-all.
To ignore an alert for all future pull requests, use Socket's Dashboard to
change the triage state of this alert.
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
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.
renovate
bot
force-pushed
the
renovate/npm-next-vulnerability
branch
from
This PR contains the following updates:
14.2.35→15.0.8GitHub Vulnerability Alerts
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: #64553isolated-vmto server-external-packages.json: #64749next experimental-testcommand: #6435214898b6toc3048aa: #64798squooshin favor ofsharpas optional dependency: #63321@swc/coretov1.5.0: #65022nextWebpack alias last: #65123Configuration
📅 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.