fix(deps): update dependency next to v15 [security] by renovate[bot] · Pull Request #495 · mooseburgr/plex-utils

renovate · 2026-02-02T20:15:01Z

This PR contains the following updates:

Package	Change	Age	Confidence
next (source)	`^13.5.11` → `^15.0.0`

Next.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 Host header 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

Next.js (<14.1.1) is running in a self-hosted* manner.
The Next.js application makes use of Server Actions.
The Server Action performs a redirect to a relative path which starts with a /.

* 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 Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Denial of Service condition in Next.js image optimization

CVE-2024-47831 / GHSA-g77x-44xx-532m

More information

Details

Impact

The image optimization feature of Next.js contained a vulnerability which allowed for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption.

Not affected:

The next.config.js file is configured with images.unoptimized set to true or images.loader set to a non-default value.
The Next.js application is hosted on Vercel.

Patches

This issue was fully patched in Next.js 14.2.7. We recommend that users upgrade to at least this version.

Workarounds

Ensure that the next.config.js file has either images.unoptimized, images.loader or images.loaderFile assigned.

Credits

Brandon Dahler (brandondahler), AWS
Dimitrios Vlastaras

Severity

CVSS Score: 4.6 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js authorization bypass vulnerability

CVE-2024-51479 / GHSA-7gfc-8cq8-jh5f

More information

Details

Impact

If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed.

Patches

This issue was patched in Next.js 14.2.15 and later.

If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version.

Workarounds

There are no official workarounds for this vulnerability.

Credits

We'd like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Information exposure in Next.js dev server due to lack of origin verification

CVE-2025-48068 / GHSA-3h52-269p-cp9r

More information

Details

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 dev is active.

Because the mitigation is potentially a breaking change for some development setups, to opt-in to the fix, you must configure allowedDevOrigins in 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.

Severity

CVSS Score: 2.3 / 10 (Low)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js Affected by Cache Key Confusion for Image Optimization API Routes

CVE-2025-57752 / GHSA-g5qg-72qw-gw5v

More information

Details

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 or Authorization), 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

Severity

CVSS Score: 6.2 / 10 (Medium)
Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js Content Injection Vulnerability for Image Optimization

CVE-2025-55173 / GHSA-xv57-4mr9-wg8v

More information

Details

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 or images.remotePatterns are encouraged to upgrade and verify that external image sources are strictly validated.

More details at Vercel Changelog

Severity

CVSS Score: 4.3 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js Improper Middleware Redirect Handling Leads to SSRF

CVE-2025-57822 / GHSA-4342-x723-ch2f

More information

Details

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

Severity

CVSS Score: 6.5 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js Race Condition to Cache Poisoning

CVE-2025-32421 / GHSA-qpjv-v59x-3qc4

More information

Details

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.

Severity

CVSS Score: 3.7 / 10 (Low)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next Vulnerable to Denial of Service with Server Components

GHSA-mwv6-3258-q52c

More information

Details

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.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up

GHSA-5j59-xgg2-r9c4

More information

Details

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.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration

CVE-2025-59471 / GHSA-9g9p-9gw9-jx7f

More information

Details

A DoS vulnerability exists in self-hosted Next.js applications that have remotePatterns configured 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 that remotePatterns is 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.

Severity

CVSS Score: 5.9 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components

GHSA-h25m-26qc-wcjf

More information

Details

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.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades

CVE-2026-44578 / GHSA-c4j6-fc7j-m34r

More information

Details

Impact

Self-hosted applications using the built-in Node.js server can be vulnerable to server-side request forgery through crafted WebSocket upgrade requests. An attacker can cause the server to proxy requests to arbitrary internal or external destinations, which may expose internal services or cloud metadata endpoints. Vercel-hosted deployments are not affected.

Fix

We now apply the same safety checks to WebSocket upgrade handling that already existed for normal HTTP requests, so upgrade requests are only proxied when routing has explicitly marked them as safe external rewrites.

Workarounds

If you cannot upgrade immediately, do not expose the origin server directly to untrusted networks. If WebSocket upgrades are not required, block them at your reverse proxy or load balancer, and restrict origin egress to internal networks and metadata services where possible.

Severity

CVSS Score: 8.6 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js Vulnerable to Denial of Service with Server Components

GHSA-8h8q-6873-q5fj

More information

Details

A vulnerability affects certain React Server Components packages for versions 19.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-23870.

A specially crafted HTTP request can be sent to any App Router Server Function endpoint that, when deserialized, may trigger excessive CPU usage. This can result in denial of service in unpatched environments.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js has cross-site scripting in beforeInteractive scripts with untrusted input

CVE-2026-44580 / GHSA-gx5p-jg67-6x7h

More information

Details

Impact

Applications that use beforeInteractive scripts together with untrusted content can be vulnerable to cross-site scripting. In affected versions, serialized script content was not escaped safely before being embedded into the document, which could allow attacker-controlled input to break out of the intended script context and execute arbitrary JavaScript in a visitor's browser.

Fix

We now HTML-escape serialized beforeInteractive script content before embedding it into the page, preventing attacker-controlled content from breaking out of the inline script boundary.

Workarounds

If you cannot upgrade immediately, do not pass untrusted data into beforeInteractive scripts. If that pattern is unavoidable, sanitize or escape the content before embedding it.

Severity

CVSS Score: 6.1 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

CVE-2026-44573 / GHSA-36qx-fr4f-26g5

More information

Details

Impact

Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks.

Fix

The matcher logic was updated to perform the same match as it would on a non-i18n data route.

Workarounds

If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.

Severity

CVSS Score: 7.5 / 10 (High)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js's Middleware / Proxy redirects can be cache-poisoned

CVE-2026-44572 / GHSA-3g8h-86w9-wvmq

More information

Details

Impact

Next.js uses the x-nextjs-data request header for internal data requests. On affected versions, an external client could send this header on a normal request to a path handled by middleware that returns a redirect.

When that happened, the middleware/proxy could treat the request as a data request and replace the standard Location redirect header with the internal x-nextjs-redirect header. Browsers do not follow x-nextjs-redirect, so the response became an unusable redirect for normal clients.

If the application was deployed behind a CDN or reverse proxy that caches 3xx responses without varying on this header, a single attacker request could poison the cached redirect response for the affected path. Subsequent visitors could then receive a cached redirect response without a Location header, causing a denial of service for that redirect path until the cache entry expired or was purged.

Affected scenarios

This affects applications that:

use middleware or proxy redirects
are deployed behind a caching CDN or reverse proxy
allow 3xx responses on those paths to be cached without differentiating internal data requests from normal requests

Fix

The fix stops trusting x-nextjs-data by itself for middleware redirect handling. A request is now treated as an internal data request only when it is validated as such by internal routing state, preserving legitimate data-request redirect behavior while preventing external header injection from changing normal redirect responses.

Workarounds

Before upgrading, users can reduce risk by:

configuring the CDN or reverse proxy to vary its cache key on x-nextjs-data for affected responses

Severity

CVSS Score: 3.7 / 10 (Low)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Next.js has a Denial of Service in the Image Optimization API

CVE-2026-44577 / GHSA-h64f-5h5j-jqjh

More information

Details

Impact

When self-hosting Next.js with the default image loader, the Image Optimization API fetches local images entirely into memory without enforcing a maximum size limit. An attacker could cause out-of-memory conditions by requesting large local assets from the /_next/image endpoint that match the images.localPatterns configuration (by default, all patterns are allowed).

If you are using images.localPatterns, only the patterns in that array are impacted.
If you are using images.unoptimized: true, you are NOT impacted.
If you are using images.loader: 'custom', you are NOT impacted.
If you are using Vercel, you are NOT impacted.

Fix

We now apply response size limits consistently to internal image fetches, not just external ones, and fail oversized responses before they can exhaust process memory.

This can be adjusted using the images.maximumResponseBody configuration.

Workarounds

If you cannot upgrade immediately, avoid routing large local assets through /_next/image, disable image optimization for large or untrusted local files, or block image optimization access to those assets at the edge.

You can disable using the images.localPatterns: [] configuration. This will still allow fetching remote images (which is not impacted).

Severity

CVSS Score: 5.9 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

Release Notes

vercel/next.js (next)

`v15.5.16`

Compare Source

`v15.5.15`

Compare Source

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summary-of-cve-2026-23869

fix unlock in publish-native

This is a re-release of v15.5.11 applying the turbopack changes.

`v15.5.11`

Compare Source

Core Changes

Tracing: Fix memory leak in span map (#85529)
fix: ensure LRU cache items have minimum size of 1 to prevent unbounded growth (#89134)
Turbopack: fix NFT tracing of sharp 0.34 (#82340)
Turbopack: support pattern into exports field (#82757)
NFT tracing fixes (#84155 and #85323)
Turbopack: validate CSS without computing all paths (#83810)
feat: implement LRU cache with invocation ID scoping for minimal mode response cache (#89129)

Credits

Huge thanks to @timneutkens, @mischnic, @ztanner, and @wyattjoh for helping!

`v15.5.10`

Compare Source

Please refer the following changelogs for more information about this security release:

`v15.5.9`

Compare Source

`v15.5.8`

Compare Source

`v15.5.7`

Compare Source

`v15.5.6`

Compare Source

Core Changes

Turbopack: don't define process.cwd() in node_modules #83452

Credits

Huge thanks to @mischnic for helping!

`v15.5.5`

Compare Source

Core Changes

Split code-frame into separate compiled package (#84238)
Add deprecation warning to Runtime config (#84650)
fix: unstable_cache should perform blocking revalidation during ISR revalidation (#84716)
feat: experimental.middlewareClientMaxBodySize body cloning limit (#84722)
fix: missing next/link types with typedRoutes (#84779)

Misc Changes

docs: early October improvements and fixes (#84334)

Credits

Huge thanks to @devjiwonchoi, @ztanner, and @icyJoseph for helping!

`v15.5.4`

Compare Source

Core Changes

fix: ensure onRequestError is invoked when otel enabled (#83343)
fix: devtools initial position should be from next config (#83571)
[devtool] fix overlay styles are missing (#83721)
Turbopack: don't match dynamic pattern for node_modules packages (#83176)
Turbopack: don't treat metadata routes as RSC (#82911)
[turbopack] Improve handling of symlink resolution errors in track_glob and read_glob (#83357)
Turbopack: throw large static metadata error earlier (#82939)
fix: error overlay not closing when backdrop clicked (#83981)
Turbopack: flush Node.js worker IPC on error (#84077)

Misc Changes

[CNA] use linter preference (#83194)
CI: use KV for test timing data (#83745)
docs: september improvements and fixes (#83997)

Credits

Huge thanks to @yiminghe, @huozhi, @devjiwonchoi, @mischnic, @lukesandberg, @ztanner, @icyJoseph, @leerob, @fufuShih, @dwrth, @aymericzip, @obendev, @molebox, @OoMNoO, @pontasan, @styfle, @HondaYt, @ryuapp, @lpalmes, and @ijjk for helping!

`v15.5.3`

Compare Source

Core Changes

fix: validation return types of pages API routes (#83069)
fix: relative paths in dev in validator.ts (#83073)
fix: remove satisfies keyword from type validation to preserve old TS compatibility (#83071)

Credits

Huge thanks to @bgub for helping!

`v15.5.2`

Compare Source

Core Changes

fix: disable unknownatrules lint rule entirely (#83059)
revert: add ?dpl to fonts in /_next/static/media (#83062)

Credits

Huge thanks to @bgub and @ztanner for helping!

`v15.5.1`

Compare Source

Core Changes

fix: aliased navigations should apply scroll handling (#82900)
Turbopack: fix invalid NFT entry with file behind symlink (#82887)
fix: typesafe linking to route handlers and pages API routes (#82858)
fix: change "noUnknownAtRules" to "warn" for Biome (#82974)
fix: add path normalization to getRelativePath for Windows (#82918)
feat: add typesafety with config.typedRoutes to redirect() and permanentRedirect() (#82860)
fix: avoid importing types that will be unused (#82856)
fix: update the config.api.responseLimit type (#82852)
fix: update validation return types (#82854)

Credits

Huge thanks to @bgub, @mischnic, and @ztanner for helping!

`v15.5.0`

Compare Source

Core Changes

Use and enforce exhaustive switch statements for work unit store: #81577
Enable @typescript-eslint/switch-exhaustiveness-check rule: #81583
[dynamicIO] use RSC dynamicness to control partial vs complete PPR result: #81627
[dynamicIO] Do not use React.unstable_postpone(): #81652
feat: new detachable panel UI: #81483
Turbopack: content-hash PageLoaderAsset: #81450
[segment explorer] fix content overflow styling: #81649
Improve reliability of owner stacks for async I/O errors: #81501
fix(router): Prevent redirect loop on root data requests with basePath: #81096
Ensure custom NextServer config is honored: #81681
Fix before interactive incorrectly render css: #81146
perf: memorize exclude function in webpack config: #81525
Also enforce experimental features when there's no next config file: #81679
feat(next/image): warn when images.qualities is undefined: #81690
feat(build): optimize filterUniqueParamsCombinations to generate sub-combinations: #81321
Update NextAdapter type and re-export: #81692
upgrade to path-to-regexp@6.3.0: #80123
[metadata] replace for initial body icon case: #81688
[segment explorer] remove dev panel ui flag: #81670
Simplify running test apps locally with ppr or dynamicIO enabled: #81668
[turbopack] Return cached Promise from __turbopack_load_by_url__ : #81663
Upgrade React from 97cdd5d3-20250710 to 2f0e7e57-20250715: #81678
Delete unused renderToString function: #81707
Discard prerendered route handler data from FS cache after revalidation: #81611
Upgrade React from 2f0e7e57-20250715 to d85ec5f5-20250716: #81708
Ignore pending revalidations during prerendering: #81621
[turbopack] Clear chunk cache on HMR instead of creating new next-server VM: #81664
fix: rootParams should throw in client when fallbackParams are not present: #81711
perf(build): optimize buildAppStaticPaths performance and add helper function: #81386
Turbopack: Support string without options for @next/mdx: #81713
[Segment Cache] Support dynamic head prefetching: #81677
[sourcemaps] Consistent cursor columns: #81375
fix: revert client segment route changes for sub shell generation: #81731
fix: pages router metadata bugs with React 19: #81733
Improve error handling for headers/cookies/draftMode in 'use cache': #81716
[devtool] fix duplicate rendered indicator on server: #81729
[devtool] enable segment explorer by default: #81737
[turbopack] Stop exposing globals from Turbopack runtime: #81727
Remove unnecessary await: #81761
[chore] bump zod to latest v3: #81757
feat(turbopack): Log anonymized internal error (panic) information to telemetry: #81272
fix: revert client segment route changes for sub shell generation: #81740
bugfix: static resources staleTime should be renewed once refetched: #81771
[devtool] move font styling to global.css: #81782
[devtool] copy decoded info of error details: #81735
fix(build): add sourcePage context for PPR dynamic route lambda creation: #81781
refactor: rename experimental.dynamicIO to experimental.cacheComponents: #81562
Properly handle hanging promise rejections during prerendering: #81754
Upgrade React from d85ec5f5-20250716 to dffacc7b-20250717: #81767
Refactor: Get rid of overly generic getExpectedRequestStore function: #81791
[devtool] migrate c

Configuration

📅 Schedule: (UTC)

Branch creation
- ""
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.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

vercel · 2026-02-02T20:15:06Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
plex-utils	Error		May 12, 2026 0:02am

renovate Bot requested a review from mooseburgr as a code owner February 2, 2026 20:15

vercel Bot had a problem deploying to Preview February 2, 2026 20:15 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 3553a15 to 2386ea9 Compare February 6, 2026 10:03

renovate Bot changed the title ~~fix(deps): update dependency next to v15 [security]~~ fix(deps): update dependency next to v14 [security] Feb 6, 2026

vercel Bot had a problem deploying to Preview February 6, 2026 10:03 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 2386ea9 to 3b778b7 Compare February 12, 2026 10:01

vercel Bot had a problem deploying to Preview February 12, 2026 10:02 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 3b778b7 to 0c04e5d Compare February 14, 2026 20:47

renovate Bot changed the title ~~fix(deps): update dependency next to v14 [security]~~ fix(deps): update dependency next to v15 [security] Feb 14, 2026

vercel Bot had a problem deploying to Preview February 14, 2026 20:47 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 0c04e5d to c504053 Compare February 17, 2026 20:46

vercel Bot had a problem deploying to Preview February 17, 2026 20:47 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from c504053 to 06b6f6d Compare February 21, 2026 09:26

renovate Bot changed the title ~~fix(deps): update dependency next to v15 [security]~~ fix(deps): update dependency next to v14 [security] Feb 21, 2026

vercel Bot had a problem deploying to Preview February 21, 2026 09:26 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 1330598 to ac15f67 Compare March 9, 2026 13:13

vercel Bot had a problem deploying to Preview March 9, 2026 13:15 Failure

renovate Bot changed the title ~~fix(deps): update dependency next to v14 [security]~~ fix(deps): update dependency next to v15 [security] Mar 14, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from ac15f67 to c70b4d4 Compare April 1, 2026 17:41

vercel Bot had a problem deploying to Preview April 1, 2026 17:42 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from c70b4d4 to 57dae0c Compare April 8, 2026 17:43

vercel Bot had a problem deploying to Preview April 8, 2026 17:44 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 57dae0c to 534c6ec Compare April 13, 2026 14:40

vercel Bot had a problem deploying to Preview April 13, 2026 14:41 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 534c6ec to 7084e9b Compare April 29, 2026 19:09

vercel Bot had a problem deploying to Preview April 29, 2026 19:10 Failure

fix(deps): update dependency next to v15 [security]

a11b463

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 7084e9b to a11b463 Compare May 12, 2026 12:01

vercel Bot had a problem deploying to Preview May 12, 2026 12:02 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update dependency next to v15 [security]#495

fix(deps): update dependency next to v15 [security]#495
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-next-vulnerability

renovate Bot commented Feb 2, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Feb 2, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Feb 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Next.js Server-Side Request Forgery in Server Actions

Details

Impact

Prerequisites

Patches

Workarounds

Credit

Severity

References

Denial of Service condition in Next.js image optimization

Details

Impact

Patches

Workarounds

Credits

Severity

References

Next.js authorization bypass vulnerability

Details

Impact

Patches

Workarounds

Credits

Severity

References

Information exposure in Next.js dev server due to lack of origin verification

Details

Summary

Credit

Severity

References

Next.js Affected by Cache Key Confusion for Image Optimization API Routes

Details

Severity

References

Next.js Content Injection Vulnerability for Image Optimization

Details

Severity

References

Next.js Improper Middleware Redirect Handling Leads to SSRF

Details

Severity

References

Next.js Race Condition to Cache Poisoning

Details

Severity

References

Next Vulnerable to Denial of Service with Server Components

Details

Severity

References

Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up

Details

Severity

References

Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration

Details

Severity

References

Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components

Details

Severity

References

Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades

Details

Impact

Fix

Workarounds

Severity

References

Next.js Vulnerable to Denial of Service with Server Components

Details

Severity

References

Next.js has cross-site scripting in beforeInteractive scripts with untrusted input

Details

Impact

renovate Bot commented Feb 2, 2026 •

edited

Loading