Update dependency next to v15.5.15 [SECURITY] by renovate[bot] · Pull Request #389 · dingyi/ding.one

renovate · 2025-01-03T21:53:05Z

This PR contains the following updates:

Package	Change	Age	Confidence
next (source)	`15.1.0` → `15.5.15`

XSS in Image Optimization API for Next.js

CVE-2021-39178 / GHSA-9gr3-7897-pp7m

More information

Details

Impact

Affected: All of the following must be true to be affected
- Next.js between version 10.0.0 and 11.1.0
- The next.config.js file has images.domains array assigned
- The image host assigned in images.domains allows user-provided SVG
Not affected: The next.config.js file has images.loader assigned to something other than default
Not affected: Deployments on Vercel are not affected

Patches

Next.js v11.1.1

Severity

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

References

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

Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0

CVE-2022-23646 / GHSA-fmvm-x8mv-47mj

More information

Details

Next.js is a React framework. Starting with version 10.0.0 and prior to version 12.1.0, Next.js is vulnerable to User Interface (UI) Misrepresentation of Critical Information. In order to be affected, the next.config.js file must have an images.domains array assigned and the image host assigned in images.domains must allow user-provided SVG. If the next.config.js file has images.loader assigned to something other than default, the instance is not affected. Version 12.1.0 contains a patch for this issue. As a workaround, change next.config.js to use a different loader configuration other than the default.

Impact

Affected: All of the following must be true to be affected
- Next.js between version 10.0.0 and 12.0.10
- The next.config.js file has images.domains array assigned
- The image host assigned in images.domains allows user-provided SVG
Not affected: The next.config.js file has images.loader assigned to something other than default

Patches

Next.js 12.1.0

Workarounds

Change next.config.js to use a different loader configuration other than the default, for example:

module.exports = {
  images: {
    loader: 'imgix',
    path: 'https://example.com/myaccount/',
  },
}

Or if you want to use the loader prop on the component, you can use custom:

module.exports = {
  images: {
    loader: 'custom',
  },
}

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:H/A:N

References

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

Unexpected server crash in Next.js.

CVE-2021-43803 / GHSA-25mp-g6fv-mqxx

More information

Details

Next.js is a React framework. In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5, Node.js above 15.0.0, and next start or a custom server. Deployments on Vercel are not affected, along with similar environments where invalid requests are filtered before reaching Next.js. Versions 12.0.5 and 11.1.3 contain patches for this issue. Note that prior version 0.9.9 package next hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.

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).

Open Redirect in Next.js

CVE-2021-37699 / GHSA-vxf5-wxwp-m7g9

More information

Details

Next.js is an open source website development framework to be used with the React library. In affected versions specially encoded paths could be used when pages/_error.js was statically generated, allowing an open redirect to occur to an external site. In general, this redirect does not directly harm users although it can allow for phishing attacks by redirecting to an attacker's domain from a trusted domain.

Impact

Affected: Users of Next.js between 10.0.5 and 10.2.0
Affected: Users of Next.js between 11.0.0 and 11.0.1 using pages/_error.js without getInitialProps
Affected: Users of Next.js between 11.0.0 and 11.0.1 using pages/_error.js and next export
Not affected: Deployments on Vercel (vercel.com) are not affected
Not affected: Deployments with pages/404.js
Note that versions prior to 0.9.9 package next npm package hosted a different utility (0.4.1 being the latest version of that codebase), and this advisory does not apply to those versions.

We recommend upgrading to the latest version of Next.js to improve the overall security of your application.

Patches

https://github.com/vercel/next.js/releases/tag/v11.1.0

Severity

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

References

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

Next.js missing cache-control header may lead to CDN caching empty reply

CVE-2023-46298 / GHSA-c59h-r6p8-q9wc

More information

Details

Next.js before 13.4.20-canary.13 lacks a cache-control header and thus empty prefetch responses may sometimes be cached by a CDN, causing a denial of service to all users requesting the same URL via that CDN. Cloudflare considers these requests cacheable assets.

Severity

Low

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).

Next.js Allows a Denial of Service (DoS) with Server Actions

CVE-2024-56332 / GHSA-7m27-7ghc-44w9

More information

Details

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-Length header 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.

Severity

CVSS Score: 5.3 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:L/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).

Authorization Bypass in Next.js Middleware

CVE-2025-29927 / GHSA-f82v-jwr5-mffw

More information

Details

Impact

It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.

Patches

For Next.js 15.x, this issue is fixed in 15.2.3
For Next.js 14.x, this issue is fixed in 14.2.25
For Next.js 13.x, this issue is fixed in 13.5.9
For Next.js 12.x, this issue is fixed in 12.3.5
For Next.js 11.x, consult the below workaround.

Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.

Workaround

If patching to a safe version is infeasible, we recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application.

Credits

Allam Rachid (zhero;)
Allam Yasser (inzo_)

Severity

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

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 vulnerability can lead to DoS via cache poisoning

CVE-2025-49826 / GHSA-67rr-84xm-4c7r

More information

Details

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

Allam Rachid zhero;
Allam Yasser (inzo)

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 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 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 is vulnerable to RCE in React flight protocol

GHSA-9qr9-h5gf-34mp

More information

Details

A vulnerability affects certain React packages¹ for versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 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-55182.

Fixed in:
React: 19.0.1, 19.1.2, 19.2.1
Next.js: 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7, 15.6.0-canary.58, 16.1.0-canary.12+

The vulnerability also affects experimental canary releases starting with 14.3.0-canary.77. Users on any of the 14.3 canary builds should either downgrade to a 14.x stable release or 14.3.0-canary.76.

All users of stable 15.x or 16.x Next.js versions should upgrade to a patched, stable version immediately.

¹ The affected React packages are:

react-server-dom-parcel
react-server-dom-turbopack
react-server-dom-webpack

Severity

CVSS Score: 10.0 / 10 (Critical)
Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 smuggling in rewrites

CVE-2026-29057 / GHSA-ggv3-7p47-pfv8

More information

Details

Summary

When Next.js rewrites proxy traffic to an external backend, a crafted DELETE/OPTIONS request using Transfer-Encoding: chunked could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes.

Impact

An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel.

Patches

The vulnerability originated in an upstream library vendored by Next.js. It is fixed by updating that dependency’s behavior so content-length: 0 is added only when both content-length and transfer-encoding are absent, and transfer-encoding is no longer removed in that code path.

Workarounds

If upgrade is not immediately possible:

Block chunked DELETE/OPTIONS requests on rewritten routes at your edge/proxy.
Enforce authentication/authorization on backend routes per our security guidance.

Severity

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

References

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

Next.js: Unbounded next/image disk cache growth can exhaust storage

CVE-2026-27980 / GHSA-3x4c-7xq6-9pq8

More information

Details

Summary

The default Next.js image optimization disk cache (/_next/image) did not have a configurable upper bound, allowing unbounded cache growth.

Impact

An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. Note that this does not impact platforms that have their own image optimization capabilities, such as Vercel.

Patches

Fixed by adding an LRU-backed disk cache with images.maximumDiskCacheSize, including eviction of least-recently-used entries when the limit is exceeded. Setting maximumDiskCacheSize: 0 disables disk caching.

Workarounds

If upgrade is not immediately possible:

Periodically clean .next/cache/images.
Reduce variant cardinality (e.g., tighten values for images.localPatterns, images.remotePatterns, and images.qualities)

Severity

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

References

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

Next.js has a Denial of Service with Server Components

GHSA-q4gf-8mx6-v5v3

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-23869. You can read more about this advisory our this changelog.

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).

Release Notes

vercel/next.js (next)

`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):

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 · 2025-01-03T21:53:07Z

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

Project	Deployment	Actions	Updated (UTC)
ding-one	Error		Apr 13, 2026 1:10am

height · 2025-01-03T21:53:08Z

codesandbox · 2025-01-03T21:53:08Z

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

what-the-diff · 2025-01-03T21:53:18Z

PR Summary

Package Version Update
This pull request updates the version of the next package from 15.1.0 to 15.1.2. This change ensures that our software is running the latest stable version, ensuring performance improvements and possible bug fixes that come with the latest version.

vercel Bot had a problem deploying to Preview January 3, 2025 21:53 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from cab18aa to b4914c2 Compare March 21, 2025 18:04

renovate Bot changed the title ~~Update dependency next to v15.1.2 [SECURITY]~~ Update dependency next to v15.2.3 [SECURITY] Mar 21, 2025

vercel Bot had a problem deploying to Preview March 21, 2025 18:04 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from b4914c2 to ea8f3d6 Compare August 10, 2025 14:28

vercel Bot had a problem deploying to Preview August 10, 2025 14:29 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from ea8f3d6 to e08b23b Compare August 31, 2025 10:52

renovate Bot changed the title ~~Update dependency next to v15.2.3 [SECURITY]~~ Update dependency next to v15.4.7 [SECURITY] Aug 31, 2025

vercel Bot had a problem deploying to Preview August 31, 2025 10:53 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from e08b23b to 0e9a29c Compare September 25, 2025 16:37

vercel Bot had a problem deploying to Preview September 25, 2025 16:38 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 0e9a29c to 9aee13b Compare October 21, 2025 10:53

vercel Bot had a problem deploying to Preview October 21, 2025 10:53 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 9aee13b to 8fadcc0 Compare November 11, 2025 02:35

vercel Bot had a problem deploying to Preview November 11, 2025 02:36 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 8fadcc0 to d0459c5 Compare November 18, 2025 09:50

vercel Bot had a problem deploying to Preview November 18, 2025 09:51 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from d0459c5 to cb35ac5 Compare December 3, 2025 19:53

vercel Bot had a problem deploying to Preview December 3, 2025 19:54 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from cb35ac5 to 5f8b054 Compare January 8, 2026 17:46

vercel Bot had a problem deploying to Preview January 8, 2026 17:47 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 5f8b054 to 314d7f7 Compare January 28, 2026 22:37

renovate Bot changed the title ~~Update dependency next to v15.4.7 [SECURITY]~~ Update dependency next to v16 [SECURITY] Jan 28, 2026

vercel Bot had a problem deploying to Preview January 28, 2026 22:38 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 314d7f7 to 966a196 Compare February 5, 2026 22:51

renovate Bot changed the title ~~Update dependency next to v16 [SECURITY]~~ Update dependency next to v15.5.10 [SECURITY] Feb 5, 2026

vercel Bot had a problem deploying to Preview February 5, 2026 22:52 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 966a196 to ff6de34 Compare March 5, 2026 20:10

vercel Bot had a problem deploying to Preview March 5, 2026 20:11 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from ff6de34 to 94b2b2a Compare March 13, 2026 11:56

vercel Bot had a problem deploying to Preview March 13, 2026 11:57 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 94b2b2a to 9b860e9 Compare March 20, 2026 13:44

renovate Bot changed the title ~~Update dependency next to v15.5.10 [SECURITY]~~ Update dependency next to v15.5.13 [SECURITY] Mar 20, 2026

vercel Bot had a problem deploying to Preview March 20, 2026 13:45 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 9b860e9 to 90c86b4 Compare March 22, 2026 21:05

renovate Bot changed the title ~~Update dependency next to v15.5.13 [SECURITY]~~ Update dependency next to v15.5.14 [SECURITY] Mar 22, 2026

vercel Bot had a problem deploying to Preview March 22, 2026 21:06 Failure

renovate Bot changed the title ~~Update dependency next to v15.5.14 [SECURITY]~~ Update dependency next to v15.5.14 [SECURITY] - autoclosed Mar 27, 2026

renovate Bot closed this Mar 27, 2026

renovate Bot deleted the renovate/npm-next-vulnerability branch March 27, 2026 01:26

renovate Bot changed the title ~~Update dependency next to v15.5.14 [SECURITY] - autoclosed~~ Update dependency next to v15.5.13 [SECURITY] Mar 29, 2026

renovate Bot reopened this Mar 29, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 90c86b4 to 40e6a6f Compare March 29, 2026 12:51

vercel Bot had a problem deploying to Preview March 29, 2026 12:52 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 40e6a6f to 04cb5e3 Compare March 30, 2026 21:21

renovate Bot changed the title ~~Update dependency next to v15.5.13 [SECURITY]~~ Update dependency next to v15.5.14 [SECURITY] Mar 30, 2026

vercel Bot had a problem deploying to Preview March 30, 2026 21:21 Failure

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 04cb5e3 to 3eaa6b9 Compare April 8, 2026 21:06

vercel Bot had a problem deploying to Preview April 8, 2026 21:07 Failure

Update dependency next to v15.5.15 [SECURITY]

f8ef2cb

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 3eaa6b9 to f8ef2cb Compare April 13, 2026 01:09

renovate Bot changed the title ~~Update dependency next to v15.5.14 [SECURITY]~~ Update dependency next to v15.5.15 [SECURITY] Apr 13, 2026

vercel Bot had a problem deploying to Preview April 13, 2026 01:10 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency next to v15.5.15 [SECURITY]#389

Update dependency next to v15.5.15 [SECURITY]#389
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/npm-next-vulnerability

renovate Bot commented Jan 3, 2025 •

edited

Loading

Uh oh!

vercel Bot commented Jan 3, 2025 •

edited

Loading

Uh oh!

height Bot commented Jan 3, 2025

Uh oh!

codesandbox Bot commented Jan 3, 2025

Uh oh!

what-the-diff Bot commented Jan 3, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Jan 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

XSS in Image Optimization API for Next.js

Details

Impact

Patches

Severity

References

Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0

Details

Impact

Patches

Workarounds

Severity

References

Unexpected server crash in Next.js.

Details

Severity

References

Open Redirect in Next.js

Details

Impact

Patches

Severity

References

Next.js missing cache-control header may lead to CDN caching empty reply

Details

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

Next.js Allows a Denial of Service (DoS) with Server Actions

Details

Impact

Patches

Workarounds

Credits

Severity

References

Authorization Bypass in Next.js Middleware

Details

Impact

Patches

Workaround

Credits

Severity

References

Next.js Race Condition to Cache Poisoning

Details

Severity

References

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

Details

Summary

Credit

Severity

References

Next.JS vulnerability can lead to DoS via cache poisoning

Details

Summary

Credits

Severity

References

Next.js Content Injection Vulnerability for Image Optimization

Details

renovate Bot commented Jan 3, 2025 •

edited

Loading