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

[renovate]

ℹ️ 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.16

---

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

• https://nvd.nist.gov/vuln/detail/CVE-2023-46298
• https://github.com/vercel/next.js/issues/45301
• https://github.com/vercel/next.js/pull/54732
• https://github.com/vercel/next.js/compare/v13.4.20-canary.12...v13.4.20-canary.13
• https://github.com/vercel/next.js/commit/20d05958ff853e9c9e42139ffec294336881c648
• https://github.com/advisories/GHSA-c59h-r6p8-q9wc

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

• https://github.com/vercel/next.js/security/advisories/GHSA-77r5-gw3j-2mpf
• https://github.com/vercel/next.js/commit/44eba020c615f0d9efe431f84ada67b81576f3f5
• https://github.com/vercel/next.js/compare/v13.5.0...v13.5.1
• https://nvd.nist.gov/vuln/detail/CVE-2024-34350
• https://github.com/advisories/GHSA-77r5-gw3j-2mpf

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

• https://github.com/vercel/next.js/security/advisories/GHSA-fr5h-rqp8-mj6g
• https://github.com/vercel/next.js/pull/62561
• https://github.com/vercel/next.js/commit/8f7a6ca7d21a97bc9f7a1bbe10427b5ad74b9085
• https://nvd.nist.gov/vuln/detail/CVE-2024-34351
• https://github.com/advisories/GHSA-fr5h-rqp8-mj6g

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

• https://github.com/vercel/next.js/security/advisories/GHSA-g77x-44xx-532m
• https://nvd.nist.gov/vuln/detail/CVE-2024-47831
• https://github.com/vercel/next.js/commit/d11cbc9ff0b1aaefabcba9afe1e562e0b1fde65a
• https://github.com/advisories/GHSA-g77x-44xx-532m

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

---

Next.js Denial of Service (DoS) condition

CVE-2024-39693 / GHSA-fq54-2j52-jc42

More information

Details

Impact

A Denial of Service (DoS) condition was identified in Next.js. Exploitation of the bug can trigger a crash, affecting the availability of the server.

This vulnerability can affect all Next.js deployments on the affected versions.

Patches

This vulnerability was resolved in Next.js 13.5 and later. We recommend that users upgrade to a safe version.

Workarounds

There are no official workarounds for this vulnerability.

Credit

• Thai Vu of flyseccorp.com
• Aonan Guan (@​0dd), Senior Cloud Security Engineer

Severity

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

References

• https://github.com/vercel/next.js/security/advisories/GHSA-fq54-2j52-jc42
• https://nvd.nist.gov/vuln/detail/CVE-2024-39693
• https://github.com/advisories/GHSA-fq54-2j52-jc42

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

• https://github.com/vercel/next.js/security/advisories/GHSA-7gfc-8cq8-jh5f
• https://github.com/vercel/next.js/commit/1c8234eb20bc8afd396b89999a00f06b61d72d7b
• https://nvd.nist.gov/vuln/detail/CVE-2024-51479
• https://github.com/vercel/next.js/releases/tag/v14.2.15
• https://github.com/advisories/GHSA-7gfc-8cq8-jh5f

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

• https://github.com/vercel/next.js/security/advisories/GHSA-7m27-7ghc-44w9
• https://nvd.nist.gov/vuln/detail/CVE-2024-56332
• https://github.com/advisories/GHSA-7m27-7ghc-44w9

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

• https://github.com/vercel/next.js/security/advisories/GHSA-f82v-jwr5-mffw
• https://github.com/vercel/next.js/commit/52a078da3884efe6501613c7834a3d02a91676d2
• https://github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48
• https://nvd.nist.gov/vuln/detail/CVE-2025-29927
• https://github.com/vercel/next.js/releases/tag/v12.3.5
• https://github.com/vercel/next.js/releases/tag/v13.5.9
• https://vercel.com/changelog/vercel-firewall-proactively-protects-against-vulnerability-with-middleware
• http://www.openwall.com/lists/oss-security/2025/03/23/3
• http://www.openwall.com/lists/oss-security/2025/03/23/4
• https://security.netapp.com/advisory/ntap-20250328-0002
• https://github.com/advisories/GHSA-f82v-jwr5-mffw

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

• https://github.com/vercel/next.js/security/advisories/GHSA-3h52-269p-cp9r
• https://vercel.com/changelog/cve-2025-48068
• https://nvd.nist.gov/vuln/detail/CVE-2025-48068
• https://github.com/advisories/GHSA-3h52-269p-cp9r

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

• https://github.com/vercel/next.js/security/advisories/GHSA-g5qg-72qw-gw5v
• https://github.com/vercel/next.js/pull/82114
• https://github.com/vercel/next.js/commit/6b12c60c61ee80cb0443ccd20de82ca9b4422ddd
• https://vercel.com/changelog/cve-2025-57752
• https://nvd.nist.gov/vuln/detail/CVE-2025-57752
• https://github.com/advisories/GHSA-g5qg-72qw-gw5v

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

• https://github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2f
• https://github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4414f2093d8
• https://vercel.com/changelog/cve-2025-57822
• https://nvd.nist.gov/vuln/detail/CVE-2025-57822
• https://github.com/advisories/GHSA-4342-x723-ch2f

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

• https://github.com/vercel/next.js/security/advisories/GHSA-xv57-4mr9-wg8v
• https://github.com/vercel/next.js/commit/6b12c60c61ee80cb0443ccd20de82ca9b4422ddd
• http://vercel.com/changelog/cve-2025-55173
• https://nvd.nist.gov/vuln/detail/CVE-2025-55173
• https://vercel.com/changelog/cve-2025-55173
• https://github.com/advisories/GHSA-xv57-4mr9-wg8v

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

• https://github.com/vercel/next.js/security/advisories/GHSA-qpjv-v59x-3qc4
• https://nvd.nist.gov/vuln/detail/CVE-2025-32421
• https://vercel.com/changelog/cve-2025-32421
• https://github.com/advisories/GHSA-qpjv-v59x-3qc4

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

• https://github.com/vercel/next.js/security/advisories/GHSA-mwv6-3258-q52c
• https://nextjs.org/blog/security-update-2025-12-11
• https://www.cve.org/CVERecord?id=CVE-2025-55184
• https://github.com/advisories/GHSA-mwv6-3258-q52c

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

• https://github.com/vercel/next.js/security/advisories/GHSA-5j59-xgg2-r9c4
• https://nvd.nist.gov/vuln/detail/CVE-2025-67779
• https://nextjs.org/blog/security-update-2025-12-11
• https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components
• https://www.cve.org/CVERecord?id=CVE-2025-55184
• https://www.facebook.com/security/advisories/cve-2025-67779
• https://github.com/advisories/GHSA-5j59-xgg2-r9c4

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

• https://github.com/vercel/next.js/security/advisories/GHSA-9g9p-9gw9-jx7f
• https://nvd.nist.gov/vuln/detail/CVE-2025-59471
• https://github.com/vercel/next.js/commit/500ec83743639addceaede95e95913398975156c
• https://github.com/vercel/next.js/commit/e5b834d208fe0edf64aa26b5d76dcf6a176500ec
• https://github.com/vercel/next.js/releases/tag/v15.5.10
• https://github.com/vercel/next.js/releases/tag/v16.1.5
• https://github.com/advisories/GHSA-9g9p-9gw9-jx7f

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

• https://github.com/facebook/react/security/advisories/GHSA-83fc-fqcc-2hmg
• https://github.com/vercel/next.js/security/advisories/GHSA-h25m-26qc-wcjf
• https://nvd.nist.gov/vuln/detail/CVE-2026-23864
• https://vercel.com/changelog/summary-of-cve-2026-23864
• https://github.com/advisories/GHSA-h25m-26qc-wcjf

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

• https://github.com/vercel/next.js/security/advisories/GHSA-ggv3-7p47-pfv8
• https://github.com/vercel/next.js/commit/dc98c04f376c6a1df76ec3e0a2d07edf4abdabd6
• https://github.com/vercel/next.js/releases/tag/v15.5.13
• https://github.com/vercel/next.js/releases/tag/v16.1.7
• https://nvd.nist.gov/vuln/detail/CVE-2026-29057
• https://github.com/advisories/GHSA-ggv3-7p47-pfv8

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

• https://github.com/vercel/next.js/security/advisories/GHSA-3x4c-7xq6-9pq8
• https://github.com/vercel/next.js/commit/39eb8e0ac498b48855a0430fbf4c22276a73b4bd
• https://github.com/vercel/next.js/releases/tag/v16.1.7
• https://nvd.nist.gov/vuln/detail/CVE-2026-27980
• https://github.com/advisories/GHSA-3x4c-7xq6-9pq8

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

• https://github.com/vercel/next.js/security/advisories/GHSA-q4gf-8mx6-v5v3
• https://vercel.com/changelog/summary-of-cve-2026-23869
• https://github.com/advisories/GHSA-q4gf-8mx6-v5v3

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

• https://github.com/vercel/next.js/security/advisories/GHSA-vfv6-92ff-j949
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44582
• https://github.com/advisories/GHSA-vfv6-92ff-j949

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

• https://github.com/vercel/next.js/security/advisories/GHSA-c4j6-fc7j-m34r
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44578
• https://github.com/advisories/GHSA-c4j6-fc7j-m34r

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

• https://github.com/facebook/react/security/advisories/GHSA-rv78-f8rc-xrxh
• https://github.com/vercel/next.js/security/advisories/GHSA-8h8q-6873-q5fj
• https://github.com/vitejs/vite-plugin-react/security/advisories/GHSA-w94c-4vhp-22gx
• https://nvd.nist.gov/vuln/detail/CVE-2026-23870
• https://github.com/advisories/GHSA-8h8q-6873-q5fj

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

• https://github.com/vercel/next.js/security/advisories/GHSA-ffhc-5mcf-pf4q
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44581
• https://github.com/advisories/GHSA-ffhc-5mcf-pf4q

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

• https://github.com/vercel/next.js/security/advisories/GHSA-gx5p-jg67-6x7h
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44580
• https://github.com/advisories/GHSA-gx5p-jg67-6x7h

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

• https://github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44573
• https://github.com/advisories/GHSA-36qx-fr4f-26g5

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

• https://github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq
• https://github.com/vercel/next.js/releases/tag/v15.5.16
• https://github.com/vercel/next.js/releases/tag/v16.2.5
• https://nvd.nist.gov/vuln/detail/CVE-2026-44572
• https://github.com/advisories/GHSA-3g8h-86w9-wvmq

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 / 1

✂ Note

PR body was truncated to here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextjs-typescript-tailwind-starter	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 9, 2025 5:28pm

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

ERROR: This version of pnpm requires at least Node.js v22.13
The current version of Node.js is v18.19.0
Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.