fix(deps): update dependency next to ^15.5.21 [security] by renovate[bot] · Pull Request #95 · contentful/experiences

renovate · 2026-07-24T18:56:54Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

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: Denial of Service in the Image Optimization API using SVGs

CVE-2026-64644 / GHSA-q8wf-6r8g-63ch

More information

Details

Impact

When self-hosting Next.js with the default image loader, the Image Optimization API can optimize remotely hosted images if configured (not enabled by default). If those images contain malicious content, they can cause CPU exhaustion in /_next/image endpoints.

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

Workarounds

If you cannot upgrade immediately, you can avoid the expensive work by setting config.experimental.imgOptSkipMetadata : true.

Severity

CVSS Score: 6.3 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/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: 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: Unbounded Server Action payload in Edge runtime

CVE-2026-64646 / GHSA-4c39-4ccg-62r3

More information

Details

Impact

Requests targeting Next.js applications using App Router with at least one Server Action can lead to excessive memory consumption if that Server Actions uses the Edge runtime

Workarounds

If you cannot upgrade, ensure your hosting provider limits the request's body size. 5 MiB should be allowed at max by your hosting provider.

Severity

CVSS Score: 6.3 / 10 (Medium)
Vector String: CVSS:4.0/AV:N/AC:L/AT:P/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: 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: Server-Side Request Forgery in Server Actions on custom servers

CVE-2026-64649 / GHSA-89xv-2m56-2m9x

More information

Details

Impact

When a Server Action forwards or redirects a request, an attacker can cause the server to send that outbound request to a malicious host (Server-Side Request Forgery). This requires the attacker's request to control Host-associated headers. In some configurations, it's also possible to obtain internal values that weaken middleware/proxy authorization.

Applications that use Server Actions are affected when the incoming host header is not fixed to a trusted value. This typically occurs on custom servers, or on deployments not behind a proxy that pins the host. Managed hosting pins the host upstream and is not affected; next start and standalone output do the same from version 14.2 onward.

Workarounds

If you cannot upgrade, ensure clients do not control the host header your application receives. Pin or validate Host and X-Forwarded-Host at your edge or proxy. On version 14.2.0 and later, you can additionally set the __NEXT_PRIVATE_ORIGIN environment variable to your deployment's real origin:

__NEXT_PRIVATE_ORIGIN=https://www.example.com node server.js

#### 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:N/SI:N/SA:N`

#### References
- [https://github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x)
- [https://github.com/vercel/next.js/commit/b51206321854193208c0805ba42acc49287f942b](https://redirect.github.com/vercel/next.js/commit/b51206321854193208c0805ba42acc49287f942b)
- [https://github.com/vercel/next.js/commit/e3e5666ccead3a15162793d697af5e48b7cc0498](https://redirect.github.com/vercel/next.js/commit/e3e5666ccead3a15162793d697af5e48b7cc0498)
- [https://github.com/vercel/next.js/releases/tag/v15.5.21](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.21)
- [https://github.com/vercel/next.js/releases/tag/v16.2.11](https://redirect.github.com/vercel/next.js/releases/tag/v16.2.11)
- [https://github.com/advisories/GHSA-89xv-2m56-2m9x](https://redirect.github.com/advisories/GHSA-89xv-2m56-2m9x)

This data is provided by the [GitHub Advisory Database](https://redirect.github.com/advisories/GHSA-89xv-2m56-2m9x) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
[GHSA-h25m-26qc-wcjf](https://redirect.github.com/advisories/GHSA-h25m-26qc-wcjf)

<details>
<summary>More information</summary>

#### 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](https://redirect.github.com/facebook/react/security/advisories/GHSA-83fc-fqcc-2hmg).

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://redirect.github.com/facebook/react/security/advisories/GHSA-83fc-fqcc-2hmg)
- [https://github.com/vercel/next.js/security/advisories/GHSA-h25m-26qc-wcjf](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-h25m-26qc-wcjf)
- [https://nvd.nist.gov/vuln/detail/CVE-2026-23864](https://nvd.nist.gov/vuln/detail/CVE-2026-23864)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://vercel.com/changelog/summary-of-cve-2026-23864](https://vercel.com/changelog/summary-of-cve-2026-23864)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-h25m-26qc-wcjf) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js Allows a Denial of Service (DoS) with Server Actions
[CVE-2024-56332](https://nvd.nist.gov/vuln/detail/CVE-2024-56332) / [GHSA-7m27-7ghc-44w9](https://redirect.github.com/advisories/GHSA-7m27-7ghc-44w9)

<details>
<summary>More information</summary>

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-7m27-7ghc-44w9)
- [https://nvd.nist.gov/vuln/detail/CVE-2024-56332](https://nvd.nist.gov/vuln/detail/CVE-2024-56332)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-7m27-7ghc-44w9) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js Race Condition to Cache Poisoning
[CVE-2025-32421](https://nvd.nist.gov/vuln/detail/CVE-2025-32421) / [GHSA-qpjv-v59x-3qc4](https://redirect.github.com/advisories/GHSA-qpjv-v59x-3qc4)

<details>
<summary>More information</summary>

#### 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](https://vercel.com/changelog/cve-2025-32421)

**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://redirect.github.com/vercel/next.js/security/advisories/GHSA-qpjv-v59x-3qc4)
- [https://nvd.nist.gov/vuln/detail/CVE-2025-32421](https://nvd.nist.gov/vuln/detail/CVE-2025-32421)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://vercel.com/changelog/cve-2025-32421](https://vercel.com/changelog/cve-2025-32421)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-qpjv-v59x-3qc4) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.JS vulnerability can lead to DoS via cache poisoning 
[CVE-2025-49826](https://nvd.nist.gov/vuln/detail/CVE-2025-49826) / [GHSA-67rr-84xm-4c7r](https://redirect.github.com/advisories/GHSA-67rr-84xm-4c7r)

<details>
<summary>More information</summary>

#### 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](https://vercel.com/changelog/cve-2025-49826)

##### Credits
- Allam Rachid [zhero;](https://zhero-web-sec.github.io/research-and-things/)
- 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
- [https://github.com/vercel/next.js/security/advisories/GHSA-67rr-84xm-4c7r](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-67rr-84xm-4c7r)
- [https://nvd.nist.gov/vuln/detail/CVE-2025-49826](https://nvd.nist.gov/vuln/detail/CVE-2025-49826)
- [https://github.com/vercel/next.js/commit/16bfce64ef2157f2c1dfedcfdb7771bc63103fd2](https://redirect.github.com/vercel/next.js/commit/16bfce64ef2157f2c1dfedcfdb7771bc63103fd2)
- [https://github.com/vercel/next.js/commit/a15b974ed707d63ad4da5b74c1441f5b7b120e93](https://redirect.github.com/vercel/next.js/commit/a15b974ed707d63ad4da5b74c1441f5b7b120e93)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://github.com/vercel/next.js/releases/tag/v15.1.8](https://redirect.github.com/vercel/next.js/releases/tag/v15.1.8)
- [https://vercel.com/changelog/cve-2025-49826](https://vercel.com/changelog/cve-2025-49826)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-67rr-84xm-4c7r) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Information exposure in Next.js dev server due to lack of origin verification
[CVE-2025-48068](https://nvd.nist.gov/vuln/detail/CVE-2025-48068) / [GHSA-3h52-269p-cp9r](https://redirect.github.com/advisories/GHSA-3h52-269p-cp9r)

<details>
<summary>More information</summary>

#### 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](https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins).

Learn more: https://vercel.com/changelog/cve-2025-48068

##### Credit

Thanks to [sapphi-red](https://redirect.github.com/sapphi-red) and [Radman Siddiki](https://redirect.github.com/R4356th) 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-3h52-269p-cp9r)
- [https://nvd.nist.gov/vuln/detail/CVE-2025-48068](https://nvd.nist.gov/vuln/detail/CVE-2025-48068)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://vercel.com/changelog/cve-2025-48068](https://vercel.com/changelog/cve-2025-48068)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-3h52-269p-cp9r) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Authorization Bypass in Next.js Middleware
[CVE-2025-29927](https://nvd.nist.gov/vuln/detail/CVE-2025-29927) / [GHSA-f82v-jwr5-mffw](https://redirect.github.com/advisories/GHSA-f82v-jwr5-mffw)

<details>
<summary>More information</summary>

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

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-f82v-jwr5-mffw) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js Affected by Cache Key Confusion for Image Optimization API Routes
[CVE-2025-57752](https://nvd.nist.gov/vuln/detail/CVE-2025-57752) / [GHSA-g5qg-72qw-gw5v](https://redirect.github.com/advisories/GHSA-g5qg-72qw-gw5v)

<details>
<summary>More information</summary>

#### 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](https://vercel.com/changelog/cve-2025-57752)

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-g5qg-72qw-gw5v)
- [https://nvd.nist.gov/vuln/detail/CVE-2025-57752](https://nvd.nist.gov/vuln/detail/CVE-2025-57752)
- [https://github.com/vercel/next.js/pull/82114](https://redirect.github.com/vercel/next.js/pull/82114)
- [https://github.com/vercel/next.js/commit/6b12c60c61ee80cb0443ccd20de82ca9b4422ddd](https://redirect.github.com/vercel/next.js/commit/6b12c60c61ee80cb0443ccd20de82ca9b4422ddd)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://vercel.com/changelog/cve-2025-57752](https://vercel.com/changelog/cve-2025-57752)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-g5qg-72qw-gw5v) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js Content Injection Vulnerability for Image Optimization
[CVE-2025-55173](https://nvd.nist.gov/vuln/detail/CVE-2025-55173) / [GHSA-xv57-4mr9-wg8v](https://redirect.github.com/advisories/GHSA-xv57-4mr9-wg8v)

<details>
<summary>More information</summary>

#### 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](https://vercel.com/changelog/cve-2025-55173)

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-xv57-4mr9-wg8v)
- [https://nvd.nist.gov/vuln/detail/CVE-2025-55173](https://nvd.nist.gov/vuln/detail/CVE-2025-55173)
- [https://github.com/vercel/next.js/commit/6b12c60c61ee80cb0443ccd20de82ca9b4422ddd](https://redirect.github.com/vercel/next.js/commit/6b12c60c61ee80cb0443ccd20de82ca9b4422ddd)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://vercel.com/changelog/cve-2025-55173](https://vercel.com/changelog/cve-2025-55173)
- [http://vercel.com/changelog/cve-2025-55173](http://vercel.com/changelog/cve-2025-55173)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-xv57-4mr9-wg8v) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js Improper Middleware Redirect Handling Leads to SSRF
[CVE-2025-57822](https://nvd.nist.gov/vuln/detail/CVE-2025-57822) / [GHSA-4342-x723-ch2f](https://redirect.github.com/advisories/GHSA-4342-x723-ch2f)

<details>
<summary>More information</summary>

#### 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](https://vercel.com/changelog/cve-2025-57822)

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-4342-x723-ch2f)
- [https://nvd.nist.gov/vuln/detail/CVE-2025-57822](https://nvd.nist.gov/vuln/detail/CVE-2025-57822)
- [https://github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4414f2093d8](https://redirect.github.com/vercel/next.js/commit/9c9aaed5bb9338ef31b0517ccf0ab4414f2093d8)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://vercel.com/changelog/cve-2025-57822](https://vercel.com/changelog/cve-2025-57822)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-4342-x723-ch2f) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
[CVE-2025-59471](https://nvd.nist.gov/vuln/detail/CVE-2025-59471) / [GHSA-9g9p-9gw9-jx7f](https://redirect.github.com/advisories/GHSA-9g9p-9gw9-jx7f)

<details>
<summary>More information</summary>

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-9g9p-9gw9-jx7f)
- [https://nvd.nist.gov/vuln/detail/CVE-2025-59471](https://nvd.nist.gov/vuln/detail/CVE-2025-59471)
- [https://github.com/vercel/next.js/commit/500ec83743639addceaede95e95913398975156c](https://redirect.github.com/vercel/next.js/commit/500ec83743639addceaede95e95913398975156c)
- [https://github.com/vercel/next.js/commit/e5b834d208fe0edf64aa26b5d76dcf6a176500ec](https://redirect.github.com/vercel/next.js/commit/e5b834d208fe0edf64aa26b5d76dcf6a176500ec)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://github.com/vercel/next.js/releases/tag/v15.5.10](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.10)
- [https://github.com/vercel/next.js/releases/tag/v16.1.5](https://redirect.github.com/vercel/next.js/releases/tag/v16.1.5)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-9g9p-9gw9-jx7f) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js: HTTP request smuggling in rewrites
[CVE-2026-29057](https://nvd.nist.gov/vuln/detail/CVE-2026-29057) / [GHSA-ggv3-7p47-pfv8](https://redirect.github.com/advisories/GHSA-ggv3-7p47-pfv8)

<details>
<summary>More information</summary>

#### 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](https://nextjs.org/docs/app/guides/data-security).

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-ggv3-7p47-pfv8)
- [https://nvd.nist.gov/vuln/detail/CVE-2026-29057](https://nvd.nist.gov/vuln/detail/CVE-2026-29057)
- [https://github.com/vercel/next.js/commit/dc98c04f376c6a1df76ec3e0a2d07edf4abdabd6](https://redirect.github.com/vercel/next.js/commit/dc98c04f376c6a1df76ec3e0a2d07edf4abdabd6)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://github.com/vercel/next.js/releases/tag/v15.5.13](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.13)
- [https://github.com/vercel/next.js/releases/tag/v16.1.7](https://redirect.github.com/vercel/next.js/releases/tag/v16.1.7)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-ggv3-7p47-pfv8) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js: Unbounded next/image disk cache growth can exhaust storage
[CVE-2026-27980](https://nvd.nist.gov/vuln/detail/CVE-2026-27980) / [GHSA-3x4c-7xq6-9pq8](https://redirect.github.com/advisories/GHSA-3x4c-7xq6-9pq8)

<details>
<summary>More information</summary>

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-3x4c-7xq6-9pq8)
- [https://nvd.nist.gov/vuln/detail/CVE-2026-27980](https://nvd.nist.gov/vuln/detail/CVE-2026-27980)
- [https://github.com/vercel/next.js/commit/39eb8e0ac498b48855a0430fbf4c22276a73b4bd](https://redirect.github.com/vercel/next.js/commit/39eb8e0ac498b48855a0430fbf4c22276a73b4bd)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://github.com/vercel/next.js/releases/tag/v16.1.7](https://redirect.github.com/vercel/next.js/releases/tag/v16.1.7)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-3x4c-7xq6-9pq8) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js has a Denial of Service with Server Components
[GHSA-q4gf-8mx6-v5v3](https://redirect.github.com/advisories/GHSA-q4gf-8mx6-v5v3)

<details>
<summary>More information</summary>

#### 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](https://redirect.github.com/facebook/react/security/advisories/GHSA-479c-33wc-g2pg). You can read more about this advisory our [this changelog](https://vercel.com/changelog/summary-of-cve-2026-23869).

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://redirect.github.com/vercel/next.js/security/advisories/GHSA-q4gf-8mx6-v5v3)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://vercel.com/changelog/summary-of-cve-2026-23869](https://vercel.com/changelog/summary-of-cve-2026-23869)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-q4gf-8mx6-v5v3) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n
[CVE-2026-44573](https://nvd.nist.gov/vuln/detail/CVE-2026-44573) / [GHSA-36qx-fr4f-26g5](https://redirect.github.com/advisories/GHSA-36qx-fr4f-26g5)

<details>
<summary>More information</summary>

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5)
- [https://nvd.nist.gov/vuln/detail/CVE-2026-44573](https://nvd.nist.gov/vuln/detail/CVE-2026-44573)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://github.com/vercel/next.js/releases/tag/v15.5.16](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.16)
- [https://github.com/vercel/next.js/releases/tag/v16.2.5](https://redirect.github.com/vercel/next.js/releases/tag/v16.2.5)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-36qx-fr4f-26g5) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js's Middleware / Proxy redirects can be cache-poisoned
[CVE-2026-44572](https://nvd.nist.gov/vuln/detail/CVE-2026-44572) / [GHSA-3g8h-86w9-wvmq](https://redirect.github.com/advisories/GHSA-3g8h-86w9-wvmq)

<details>
<summary>More information</summary>

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-3g8h-86w9-wvmq)
- [https://nvd.nist.gov/vuln/detail/CVE-2026-44572](https://nvd.nist.gov/vuln/detail/CVE-2026-44572)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://github.com/vercel/next.js/releases/tag/v15.5.16](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.16)
- [https://github.com/vercel/next.js/releases/tag/v16.2.5](https://redirect.github.com/vercel/next.js/releases/tag/v16.2.5)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-3g8h-86w9-wvmq) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js Vulnerable to Denial of Service with Server Components
[GHSA-8h8q-6873-q5fj](https://redirect.github.com/advisories/GHSA-8h8q-6873-q5fj)

<details>
<summary>More information</summary>

#### 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](https://redirect.github.com/facebook/react/security/advisories/GHSA-rv78-f8rc-xrxh). 

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://redirect.github.com/facebook/react/security/advisories/GHSA-rv78-f8rc-xrxh)
- [https://github.com/vercel/next.js/security/advisories/GHSA-8h8q-6873-q5fj](https://redirect.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://redirect.github.com/vitejs/vite-plugin-react/security/advisories/GHSA-w94c-4vhp-22gx)
- [https://nvd.nist.gov/vuln/detail/CVE-2026-23870](https://nvd.nist.gov/vuln/detail/CVE-2026-23870)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-8h8q-6873-q5fj) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades
[CVE-2026-44578](https://nvd.nist.gov/vuln/detail/CVE-2026-44578) / [GHSA-c4j6-fc7j-m34r](https://redirect.github.com/advisories/GHSA-c4j6-fc7j-m34r)

<details>
<summary>More information</summary>

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-c4j6-fc7j-m34r)
- [https://nvd.nist.gov/vuln/detail/CVE-2026-44578](https://nvd.nist.gov/vuln/detail/CVE-2026-44578)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://github.com/vercel/next.js/releases/tag/v15.5.16](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.16)
- [https://github.com/vercel/next.js/releases/tag/v16.2.5](https://redirect.github.com/vercel/next.js/releases/tag/v16.2.5)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-c4j6-fc7j-m34r) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces
[CVE-2026-44581](https://nvd.nist.gov/vuln/detail/CVE-2026-44581) / [GHSA-ffhc-5mcf-pf4q](https://redirect.github.com/advisories/GHSA-ffhc-5mcf-pf4q)

<details>
<summary>More information</summary>

#### 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://redirect.github.com/vercel/next.js/security/advisories/GHSA-ffhc-5mcf-pf4q)
- [https://nvd.nist.gov/vuln/detail/CVE-2026-44581](https://nvd.nist.gov/vuln/detail/CVE-2026-44581)
- [https://github.com/vercel/next.js](https://redirect.github.com/vercel/next.js)
- [https://github.com/vercel/next.js/releases/tag/v15.5.16](https://redirect.github.com/vercel/next.js/releases/tag/v15.5.16)
- [https://github.com/vercel/next.js/releases/tag/v16.2.5](https://redirect.github.com/vercel/next.js/releases/tag/v16.2.5)

This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-ffhc-5mcf-pf4q) and the [GitHub Advisory Database](https://redirect.github.com/github/advisory-database) ([CC-BY 4.0](https://redirect.github.com/github/advisory-database/blob/main/LICENSE.md)).
</details>

---

### Next.js has cross-site scripting in beforeInteractive scripts with untrusted input
[CVE-2026-44580](https://nvd.nist.gov/vuln/detail/CVE-2026-44580) / [GHSA-gx5p-jg67-6x7h](https://redirect.github.com/advisories/GHSA-gx5p-jg67-6x7h)

<details>
<summary>More information</summary>

#### 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-controlle

> ✂ **Note**
> 
> PR body was truncated to here.

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

9982c8a

renovate Bot added the security label Jul 24, 2026

renovate Bot requested a review from a team as a code owner July 24, 2026 18:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update dependency next to ^15.5.21 [security]#95

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

renovate Bot commented Jul 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate Bot commented Jul 24, 2026

Next.js: Denial of Service in App Router using Server Actions

Details

Impact

Workarounds

Severity

References

Next.js: Unauthenticated disclosure of internal Server Function endpoints

Details

Impact

Workarounds

Severity

References

Next.js: Denial of Service in the Image Optimization API using SVGs

Details

Impact

Workarounds

Severity

References

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

Details

Impact

Workarounds

Severity

References

Next.js: Unbounded Server Action payload in Edge runtime

Details

Impact

Workarounds

Severity

References

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

Details

Impact

Workarounds

Severity

References

Next.js: Cache confusion of response bodies for requests with bodies

Details

Impact

Workarounds

Severity

References

Next.js: Server-Side Request Forgery in Server Actions on custom servers

Details

Impact

Workarounds

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants