chore(deps): update dependency next to v15 [security] by renovate[bot] · Pull Request #1583 · 4-design/for-ui

renovate · 2024-05-09T22:21:34Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
next (source)	`13.4.19` → `15.5.24`

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

Next.js Vulnerable to HTTP Request Smuggling

CVE-2024-34350 / GHSA-77r5-gw3j-2mpf

More information

Details

Impact

Inconsistent interpretation of a crafted HTTP request meant that requests are treated as both a single request, and two separate requests by Next.js, leading to desynchronized responses. This led to a response queue poisoning vulnerability in the affected Next.js versions.

For a request to be exploitable, the affected route also had to be making use of the rewrites feature in Next.js.

Patches

The vulnerability is resolved in Next.js 13.5.1 and newer. This includes Next.js 14.x.

Workarounds

There are no official workarounds for this vulnerability. We recommend that you upgrade to a safe version.

References

https://portswigger.net/web-security/request-smuggling/advanced/response-queue-poisoning

Severity

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

References

This data is provided by the GitHub Advisory Database (CC-BY 4.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).

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

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

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 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 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 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 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: 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 vulnerable to cache poisoning via collisions in React Server Component cache-busting

CVE-2026-44582 / GHSA-vfv6-92ff-j949

More information

Details

Impact

React Server Component responses can be vulnerable to cache poisoning in deployments that rely on shared caches with insufficient response partitioning. In affected conditions, collisions in the _rsc cache-busting value can allow an attacker to poison cache entries so users receive the wrong response variant for a given URL.

Fix

We strengthened the _rsc cache-busting mechanism to make practical collisions significantly harder and to better separate response variants that should not share cache entries.

Workarounds

If you cannot upgrade immediately, ensure intermediary caches correctly honor Vary for RSC-related request headers, or disable shared caching for affected RSC responses until you can deploy a patched release.

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

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 cross-site scripting in App Router applications using CSP nonces

CVE-2026-44581 / GHSA-ffhc-5mcf-pf4q

More information

Details

Impact

App Router applications that rely on CSP nonces can be vulnerable to stored cross-site scripting when deployed behind shared caches. In affected versions, malformed nonce values derived from request headers could be reflected into rendered HTML in an unsafe way, allowing an attacker to poison cached responses and cause script execution for later visitors.

Fix

We now reject or ignore malformed nonce values before they are embedded into HTML and apply stricter nonce sanitization so request-derived nonce data cannot break out of the intended attribute context.

Workarounds

If you cannot upgrade immediately, strip inbound Content-Security-Policy request headers from untrusted traffic.

Severity

CVSS Score: 4.7 / 10 (Medium)
Vector String: CVSS:3.1/AV:N/AC:H/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 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: Denial of Service in App Router using Server Actions

CVE-2026-64641 / GHSA-m99w-x7hq-7vfj

More information

Details

Impact

Crafted requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive CPU usage blocking processing of further requests in the same process.

Workarounds

No workaround exists besides upgrading. Applications using Pages Router or not using Server Actions are not vulnerable.

Severity

CVSS Score: 8.2 / 10 (High)
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

References

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

Next.js: Unauthenticated disclosure of internal Server Function endpoints

CVE-2026-64643 / GHSA-955p-x3mx-jcvp

More information

Details

Impact

In Next.js applications using App Router, Server Actions (use server) or use cache endpoints can be disclosed bypassing any authentication on the pages where these endpoints are usually used.

Server Action IDs can be disclosed to unauthenticated users via publicly served client artifacts (for example, static chunks containing action references).

Affected users are applications using App Router + Server Actions.

By itself, this disclosure is typically a recon/enumeration primitive; however, it can increase risk when combined with other weaknesses.

Workarounds

Never assume any authentication claims at the use cache or use server boundary. Always authenticate within the boundary.

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:N/VA:N/SC:N/SI:N/SA:N

References

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

Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname

CVE-2026-64645 / GHSA-p9j2-gv94-2wf4

More information

Details

Impact

A rewrites() or redirects() rule that builds its external destination hostname from request-controlled input can be pointed at an arbitrary hostname, regardless of the rule's hostname suffix. For a rewrite, Next.js proxies the request to that arbitrary host and serves the response from the application's origin, leading to Server-Side Request forgery. A redirects() rule configured this way is vulnerable to an Open Redirect.

This affects any destination that puts a dynamic segment in the hostname, whether from the path:

// next.config.js
module.exports = {
  async rewrites() {
    return [
      {
        source: '/:tenant',
        destination: 'https://:tenant.api.example.com',
      },
    ]
  },
}

or from a has capture:

// next.config.js
module.exports = {
  async rewrites() {
    return [
      {
        source: '/',
        has: [{ type: 'query', key: 'region', value: '(?<region>.+)' }],
        destination: 'https://:region.api.example.com',
      },
    ]
  },
}

Workarounds

If you cannot upgrade immediately, do not build the hostname of an external rewrites() or redirects() destination from user-controlled input. If a dynamic subdomain is required, constrain the value to hostname-safe characters: value: '(?<region>[a-z0-9-]+)'.

Severity

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

References

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

Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences

CVE-2026-64647 / GHSA-4633-3j49-mh5q

More information

Details

Impact

A server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped.

This is only an issue when receiving request bodies with a content type charset other than UTF-8. For example, the UTF-16 byte sequences for 삃삃 and 섄섄 in the request body would share the same cache.

Workarounds

If you cannot upgrade, consider only making fetch requests with UTF-8 bodies (default in Next.js). Applications using Pages Router are not vulnerable.

Severity

CVSS Score: 6.3 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:H/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: Cache confusion of response bodies for requests with bodies

CVE-2026-64648 / GHSA-68g3-v927-f742

More information

Details

Impact

A server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped.

This only applies to fetch calls with a request that has a different init than the one passed to fetch.
Safe: fetch(new Request(init), init)
Unsafe: fetch(new Request(init), aDifferentInit)

Workarounds

No workaround exists besides upgrading. Applications using Pages Router are not vulnerable.

Severity

CVSS Score: 6.0 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/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: Unauthenticated Remote Code Execution on windows-hosted servers

CVE-2026-75604 / GHSA-p293-qw3h-jr36

More information

Details

Impact

A vulnerability in applications using Pages and App router without Cache Component can lead to remote code execution when the server is hosted on machines using a Windows filesystem.

Workaround

There is no known workaround for affected windows-hosted applications. You should upgrade immediately if your server is hosted on Windows.

Severity

CVSS Score: 9.0 / 10 (Critical)
Vector String: CVSS:3.1/AV:N/AC:H/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: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used

GHSA-2xp9-vwfh-vxw4

More information

Details

A vulnerability in the underlying libheif library used by sharp which Next.js uses for image optimization can lead to remote code execution when AVIF files are optimized.

Until a fix has propagated, optimization of AVIF files is disabled.

Severity

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

References

❗ Important

✂ PR body was truncated to here.

changeset-bot · 2024-05-09T22:21:38Z

⚠️ No Changeset found

Latest commit: 5933db4

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

cloudflare-workers-and-pages · 2024-05-09T22:24:54Z

Deploying for-ui with Cloudflare Pages

Latest commit:	`5933db4`
Status:	✅ Deploy successful!
Preview URL:	https://f3689992.for-ui.pages.dev
Branch Preview URL:	https://renovate-npm-next-vulnerabil.for-ui.pages.dev

View logs

coderabbitai · 2024-12-18T06:26:46Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: 4-design/for-ui/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: a197d93c-d054-4fa8-be37-b50f6637b174

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

qodo-code-review · 2025-03-25T03:14:52Z

Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: build-nextjs
Failed stage: Run npm run build [❌]
Failure summary: The action failed because the build process requires Node.js version 18.17.0 or higher, but the workflow is using Node.js 16.20.2. The error message clearly states: "You are using Node.js 16.20.2. For Next.js, Node.js version >= v18.17.0 is required."
Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 457: 37 packages are looking for funding 458: run `npm fund` for details 459: 5 vulnerabilities (3 moderate, 1 high, 1 critical) 460: To address issues that do not require attention, run: 461: npm audit fix 462: To address all issues, run: 463: npm audit fix --force 464: Run `npm audit` for details. 465: ##[group]Run npm run build 466: �[36;1mnpm run build�[0m 467: shell: /usr/bin/bash -e {0} 468: ##[endgroup] 469: > @4design/nextjs-app@0.1.0 build 470: > NODE_ENV=production next build 471: You are using Node.js 16.20.2. For Next.js, Node.js version >= v18.17.0 is required. 472: ##[error]Process completed with exit code 1. 473: Post job cleanup.

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from ca172d8 to 72ed184 Compare May 10, 2024 00:35

renovate Bot changed the title ~~chore(deps): update dependency next to v13.5.1 [security]~~ chore(deps): update dependency next to v14 [security] May 10, 2024

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 72ed184 to c10f130 Compare December 18, 2024 06:26

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from c10f130 to 58da64c Compare March 24, 2025 16:59

renovate Bot changed the title ~~chore(deps): update dependency next to v14 [security]~~ chore(deps): update dependency next to v13.5.9 [security] Mar 24, 2025

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 58da64c to 5fdee48 Compare March 25, 2025 03:12

renovate Bot changed the title ~~chore(deps): update dependency next to v13.5.9 [security]~~ chore(deps): update dependency next to v14 [security] Mar 25, 2025

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 677215c to d860b22 Compare May 17, 2025 06:30

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from d860b22 to 5b5ade4 Compare June 14, 2025 04:39

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from fc0a8c1 to f61250d Compare June 25, 2025 14:53

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from f61250d to 0b6133a Compare August 22, 2025 02:38

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 2f55552 to e214c13 Compare September 6, 2025 22:51

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from c254b94 to c73c3e9 Compare September 13, 2025 22:13

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 4 times, most recently from bd51c31 to 88c4ba2 Compare September 23, 2025 02:33

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from ac55214 to 1436e1f Compare September 30, 2025 01:39

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 1436e1f to d5bfb38 Compare November 17, 2025 03:01

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 308a050 to d5765a8 Compare December 13, 2025 09:01

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 36b4a64 to aeb8b65 Compare January 9, 2026 13:30

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from aeb8b65 to d659d2e Compare February 3, 2026 15:02

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

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from d659d2e to 1251865 Compare February 6, 2026 02:04

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

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 1251865 to 387260a Compare February 12, 2026 16:42

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

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 387260a to 670d3f0 Compare February 14, 2026 10:09

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

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 670d3f0 to 52c4699 Compare March 6, 2026 05:19

renovate Bot changed the title ~~chore(deps): update dependency next to v14 [security]~~ chore(deps): update dependency next to v13.5.9 [security] Mar 6, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 52c4699 to 0212b56 Compare March 14, 2026 05:22

renovate Bot changed the title ~~chore(deps): update dependency next to v13.5.9 [security]~~ chore(deps): update dependency next to v14 [security] Mar 14, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 0212b56 to 7d35bd6 Compare March 18, 2026 14:00

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 7d35bd6 to 5d51172 Compare March 31, 2026 11:49

renovate Bot changed the title ~~chore(deps): update dependency next to v14 [security]~~ chore(deps): update dependency next to v14 [security] - autoclosed Apr 27, 2026

renovate Bot closed this Apr 27, 2026

renovate Bot deleted the renovate/npm-next-vulnerability branch April 27, 2026 18:05

renovate Bot changed the title ~~chore(deps): update dependency next to v14 [security] - autoclosed~~ chore(deps): update dependency next to v14 [security] Apr 27, 2026

renovate Bot reopened this Apr 27, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from 5d51172 to 2baf71b Compare April 27, 2026 21:15

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 2baf71b to 6ea3c01 Compare May 9, 2026 22:57

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from 6ea3c01 to d870cdf Compare August 26, 2026 14:48

renovate Bot changed the title ~~chore(deps): update dependency next to v14 [security]~~ chore(deps): update dependency next to v15 [security] Aug 30, 2026

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from d870cdf to e803934 Compare September 9, 2026 19:06

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

5933db4

renovate Bot force-pushed the renovate/npm-next-vulnerability branch from e803934 to 5933db4 Compare September 30, 2026 23:58

Navigation Menu

chore(deps): update dependency next to v15 [security] - #1583

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

renovate Bot commented May 9, 2024 •

edited

Loading

Uh oh!

changeset-bot Bot commented May 9, 2024 •

edited

Loading

Uh oh!

cloudflare-workers-and-pages Bot commented May 9, 2024 •

edited

Loading

Uh oh!

coderabbitai Bot commented Dec 18, 2024 •

edited

Loading

Review skipped

Uh oh!

qodo-code-review Bot commented Mar 25, 2025

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented May 9, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

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

Details

Severity

References

Next.js Vulnerable to HTTP Request Smuggling

Details

Impact

Patches

Workarounds

References

Severity

References

Next.js Server-Side Request Forgery in Server Actions

Details

Impact

Prerequisites

Patches

Workarounds

Credit

Severity

References

Next.js authorization bypass vulnerability

Details

Impact

Patches

Workarounds

Credits

Severity

References

Authorization Bypass in Next.js Middleware

Details

Impact

Patches

Workaround

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 Improper Middleware Redirect Handling Leads to SSRF

Details

Severity

References

Next.js Content Injection Vulnerability for Image Optimization

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 HTTP request deserialization can lead to DoS when using insecure React Server Components

Details

Severity

References

Next.js: HTTP request smuggling in rewrites

Details

Summary

Impact

Patches

Workarounds

renovate Bot commented May 9, 2024 •

edited

Loading