next 15.0.5 vulnerabilities

Direct Vulnerabilities

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

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
H Server-side Request Forgery (SSRF) next is a react framework. Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the `resolve-routes`. An attacker can access internal resources and potentially exfiltrate sensitive information by crafting requests containing user-controlled headers (e.g., Location) that are forwarded or interpreted without validation. Note: This is only exploitable if custom middleware logic is implemented in a self-hosted deployment. The project maintainers recommend using the documented `NextResponse.next({request})` to explicitly pass the request object. How to fix Server-side Request Forgery (SSRF)? Upgrade `next` to version 14.2.32, 15.4.2-canary.43, 15.4.7 or higher.	<14.2.32>=15.0.0 <15.4.2-canary.43>=15.4.3 <15.4.7
M Use of Cache Containing Sensitive Information next is a react framework. Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information in the image optimization process, when responses from API routes vary based on request headers such as `Cookie` or `Authorization`. An attacker can gain unauthorized access to sensitive image data by exploiting cache key confusion, causing responses intended for authenticated users to be served to unauthorized users. Note: Exploitation requires a prior authorized request to populate the cache. How to fix Use of Cache Containing Sensitive Information? Upgrade `next` to version 14.2.31, 15.4.2-canary.19, 15.4.5 or higher.	<14.2.31>=15.0.0 <15.4.2-canary.19>=15.4.3 <15.4.5
L Missing Source Correlation of Multiple Independent Data next is a react framework. Affected versions of this package are vulnerable to Missing Source Correlation of Multiple Independent Data in `image-optimizer`. An attacker can cause arbitrary files to be downloaded with attacker-controlled content and filenames by supplying malicious external image sources. Note: This is only exploitable if the application is configured to allow external image sources via the `images.domains` or `images.remotePatterns` configuration. How to fix Missing Source Correlation of Multiple Independent Data? Upgrade `next` to version 14.2.31, 15.4.2-canary.19, 15.4.5 or higher.	<14.2.31>=15.0.0 <15.4.2-canary.19>=15.4.3 <15.4.5
H HTTP Request Smuggling next is a react framework. Affected versions of this package are vulnerable to HTTP Request Smuggling that allows poisoning the browser cache with an HTTP 204 reponse for a static page, thereby denying service to other users. How to fix HTTP Request Smuggling? Upgrade `next` to version 15.1.8 or higher.	>=15.0.4-canary.51 <15.1.8
L Missing Origin Validation in WebSockets next is a react framework. Affected versions of this package are vulnerable to Missing Origin Validation in WebSockets when running next dev and the project uses the App Router. An attacker can access the source code of client components by exploiting the Cross-site WebSocket hijacking (CSWSH) attack when a user visits a malicious link while having the server running locally. How to fix Missing Origin Validation in WebSockets? Upgrade `next` to version 14.2.30, 15.2.2 or higher.	>=13.0.0 <14.2.30>=15.0.0-rc.0 <15.2.2
M Race Condition next is a react framework. Affected versions of this package are vulnerable to Race Condition in the `Pages Router`. An attacker can cause the server to serve incorrect `pageProps` data instead of the expected HTML content by exploiting a race condition between two requests, one containing the `?__nextDataRequest=1` query parameter and another with the `x-now-route-matches` header. Notes: This is only exploitable if the CDN provider caches a `200 OK` response even in the absence of explicit `cache-control` headers, enabling a poisoned response to persist and be served to subsequent users; No backend access or privileged escalation is possible through this vulnerability; Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on `200 OK` status without explicit `cache-control` headers. This is a bypass of the fix for CVE-2024-46982 How to fix Race Condition? Upgrade `next` to version 14.2.24, 15.1.6 or higher.	<14.2.24>=15.0.0 <15.1.6
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

Vulnerability

Vulnerable Version

Server-side Request Forgery (SSRF)

next is a react framework.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the resolve-routes. An attacker can access internal resources and potentially exfiltrate sensitive information by crafting requests containing user-controlled headers (e.g., Location) that are forwarded or interpreted without validation.

Note: This is only exploitable if custom middleware logic is implemented in a self-hosted deployment. The project maintainers recommend using the documented NextResponse.next({request}) to explicitly pass the request object.

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

Upgrade next to version 14.2.32, 15.4.2-canary.43, 15.4.7 or higher.

<14.2.32>=15.0.0 <15.4.2-canary.43>=15.4.3 <15.4.7

Use of Cache Containing Sensitive Information

next is a react framework.

Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information in the image optimization process, when responses from API routes vary based on request headers such as Cookie or Authorization. An attacker can gain unauthorized access to sensitive image data by exploiting cache key confusion, causing responses intended for authenticated users to be served to unauthorized users.

Note: Exploitation requires a prior authorized request to populate the cache.

How to fix Use of Cache Containing Sensitive Information?

Upgrade next to version 14.2.31, 15.4.2-canary.19, 15.4.5 or higher.

<14.2.31>=15.0.0 <15.4.2-canary.19>=15.4.3 <15.4.5

Missing Source Correlation of Multiple Independent Data

next is a react framework.

Affected versions of this package are vulnerable to Missing Source Correlation of Multiple Independent Data in image-optimizer. An attacker can cause arbitrary files to be downloaded with attacker-controlled content and filenames by supplying malicious external image sources.

Note: This is only exploitable if the application is configured to allow external image sources via the images.domains or images.remotePatterns configuration.

How to fix Missing Source Correlation of Multiple Independent Data?

Upgrade next to version 14.2.31, 15.4.2-canary.19, 15.4.5 or higher.

<14.2.31>=15.0.0 <15.4.2-canary.19>=15.4.3 <15.4.5

HTTP Request Smuggling

next is a react framework.

Affected versions of this package are vulnerable to HTTP Request Smuggling that allows poisoning the browser cache with an HTTP 204 reponse for a static page, thereby denying service to other users.

How to fix HTTP Request Smuggling?

Upgrade next to version 15.1.8 or higher.

>=15.0.4-canary.51 <15.1.8

Missing Origin Validation in WebSockets

next is a react framework.

Affected versions of this package are vulnerable to Missing Origin Validation in WebSockets when running next dev and the project uses the App Router. An attacker can access the source code of client components by exploiting the Cross-site WebSocket hijacking (CSWSH) attack when a user visits a malicious link while having the server running locally.

How to fix Missing Origin Validation in WebSockets?

Upgrade next to version 14.2.30, 15.2.2 or higher.

>=13.0.0 <14.2.30>=15.0.0-rc.0 <15.2.2

Race Condition

next is a react framework.

Affected versions of this package are vulnerable to Race Condition in the Pages Router. An attacker can cause the server to serve incorrect pageProps data instead of the expected HTML content by exploiting a race condition between two requests, one containing the ?__nextDataRequest=1 query parameter and another with the x-now-route-matches header.

Notes:

This is only exploitable if the CDN provider caches a 200 OK response even in the absence of explicit cache-control headers, enabling a poisoned response to persist and be served to subsequent users;
No backend access or privileged escalation is possible through this vulnerability;
Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on 200 OK status without explicit cache-control headers.
This is a bypass of the fix for CVE-2024-46982

How to fix Race Condition?

Upgrade next to version 14.2.24, 15.1.6 or higher.

<14.2.24>=15.0.0 <15.1.6

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

next@15.0.5 vulnerabilities

The React Framework

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically