next 13.5.4 vulnerabilities

Known vulnerabilities in the next package. This does not include vulnerabilities belonging to this package’s dependencies.

Vulnerability	Vulnerable Version
C Improper Authorization next is a react framework. Affected versions of this package are vulnerable to Improper Authorization due to the improper handling of the `x-middleware-subrequest` header. An attacker can bypass authorization checks by sending crafted requests containing this specific header. How to fix Improper Authorization? Upgrade `next` to version 12.3.5, 13.5.9, 14.2.25, 15.2.3, 15.3.0-canary.12 or higher.	>=11.1.4 <12.3.5>=13.0.0 <13.5.9>=14.0.0 <14.2.25>=15.0.0-rc.0 <15.2.3>=15.3.0-canary.0 <15.3.0-canary.12
M Allocation of Resources Without Limits or Throttling next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the Server Actions process. An attacker can cause the server to hang by constructing requests that leave Server-Actions requests pending until the hosting provider terminates the function execution. Note: This is only exploitable if there are no protections against long-running Server Action invocations. How to fix Allocation of Resources Without Limits or Throttling? Upgrade `next` to version 13.5.8, 14.2.21, 15.1.2 or higher.	>=13.0.0 <13.5.8>=14.0.0 <14.2.21>=15.0.0 <15.1.2
H Missing Authorization next is a react framework. Affected versions of this package are vulnerable to Missing Authorization when using pathname-based checks in middleware for authorization decisions. If i18n configuration is not configured, an attacker can get unintended access to pages one level under the application's root directory. e.g. `https://example.com/foo` is accessible. `https://example.com/` and `https://example.com/foo/bar` are not. Note: Only self-hosted applications are vulnerable. The vulnerability has been fixed by Vercel on the server side. How to fix Missing Authorization? Upgrade `next` to version 13.5.8, 14.2.15, 15.0.0-canary.177 or higher.	>=9.5.5 <13.5.8>=14.0.0 <14.2.15>=15.0.0-canary.0 <15.0.0-canary.177
H Uncontrolled Recursion next is a react framework. Affected versions of this package are vulnerable to Uncontrolled Recursion through the image optimization feature. An attacker can cause excessive CPU consumption by exploiting this vulnerability. How to fix Uncontrolled Recursion? Upgrade `next` to version 14.2.7, 15.0.0-canary.109 or higher.	>=10.0.0 <14.2.7>=15.0.0-canary.0 <15.0.0-canary.109
H Acceptance of Extraneous Untrusted Data With Trusted Data next is a react framework. Affected versions of this package are vulnerable to Acceptance of Extraneous Untrusted Data With Trusted Data by sending a crafted HTTP request, which allows the attacker to poison the cache of a non-dynamic server-side rendered route in the page router. This will coerce the request to cache a route that is meant to not be cached and send a `Cache-Control: s-maxage=1, a stale-while-revalidate` header, which some upstream CDNs may cache as well. Note: This is only vulnerable if: The user is using pages router The user is using non-dynamic server-side rendered routes. Users are not affected if: They are using the app router The deployments are on Vercel How to fix Acceptance of Extraneous Untrusted Data With Trusted Data? Upgrade `next` to version 13.5.7, 14.2.10 or higher.	>=13.5.1 <13.5.7>=14.0.0 <14.2.10
M Server-Side Request Forgery (SSRF) next is a react framework. Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) through the `Host` header manipulation. An attacker can make unauthorized requests appearing to originate from the server. Notes: 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 `/`. How to fix Server-Side Request Forgery (SSRF)? Upgrade `next` to version 14.1.1 or higher.	>=13.4.0 <14.1.1

Vulnerability

Vulnerable Version

Improper Authorization

next is a react framework.

Affected versions of this package are vulnerable to Improper Authorization due to the improper handling of the x-middleware-subrequest header. An attacker can bypass authorization checks by sending crafted requests containing this specific header.

How to fix Improper Authorization?

Upgrade next to version 12.3.5, 13.5.9, 14.2.25, 15.2.3, 15.3.0-canary.12 or higher.

>=11.1.4 <12.3.5>=13.0.0 <13.5.9>=14.0.0 <14.2.25>=15.0.0-rc.0 <15.2.3>=15.3.0-canary.0 <15.3.0-canary.12

Allocation of Resources Without Limits or Throttling

next is a react framework.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through the Server Actions process. An attacker can cause the server to hang by constructing requests that leave Server-Actions requests pending until the hosting provider terminates the function execution.

Note:

This is only exploitable if there are no protections against long-running Server Action invocations.

How to fix Allocation of Resources Without Limits or Throttling?

Upgrade next to version 13.5.8, 14.2.21, 15.1.2 or higher.

>=13.0.0 <13.5.8>=14.0.0 <14.2.21>=15.0.0 <15.1.2

Missing Authorization

next is a react framework.

Affected versions of this package are vulnerable to Missing Authorization when using pathname-based checks in middleware for authorization decisions. If i18n configuration is not configured, an attacker can get unintended access to pages one level under the application's root directory.

e.g. https://example.com/foo is accessible. https://example.com/ and https://example.com/foo/bar are not.

Note:

Only self-hosted applications are vulnerable. The vulnerability has been fixed by Vercel on the server side.

How to fix Missing Authorization?

Upgrade next to version 13.5.8, 14.2.15, 15.0.0-canary.177 or higher.

>=9.5.5 <13.5.8>=14.0.0 <14.2.15>=15.0.0-canary.0 <15.0.0-canary.177

Uncontrolled Recursion

next is a react framework.

Affected versions of this package are vulnerable to Uncontrolled Recursion through the image optimization feature. An attacker can cause excessive CPU consumption by exploiting this vulnerability.

How to fix Uncontrolled Recursion?

Upgrade next to version 14.2.7, 15.0.0-canary.109 or higher.

>=10.0.0 <14.2.7>=15.0.0-canary.0 <15.0.0-canary.109

Acceptance of Extraneous Untrusted Data With Trusted Data

next is a react framework.

Affected versions of this package are vulnerable to Acceptance of Extraneous Untrusted Data With Trusted Data by sending a crafted HTTP request, which allows the attacker to poison the cache of a non-dynamic server-side rendered route in the page router. This will coerce the request to cache a route that is meant to not be cached and send a Cache-Control: s-maxage=1, a stale-while-revalidate header, which some upstream CDNs may cache as well.

Note:

This is only vulnerable if:

The user is using pages router
The user is using non-dynamic server-side rendered routes.

Users are not affected if:

They are using the app router
The deployments are on Vercel

How to fix Acceptance of Extraneous Untrusted Data With Trusted Data?

Upgrade next to version 13.5.7, 14.2.10 or higher.

>=13.5.1 <13.5.7>=14.0.0 <14.2.10

Server-Side Request Forgery (SSRF)

next is a react framework.

Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) through the Host header manipulation. An attacker can make unauthorized requests appearing to originate from the server.

Notes:

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

How to fix Server-Side Request Forgery (SSRF)?

Upgrade next to version 14.1.1 or higher.

>=13.4.0 <14.1.1

next@13.5.4 vulnerabilities

The React Framework

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?