next 15.1.9 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
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
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

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

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

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

next@15.1.9 vulnerabilities

The React Framework

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

Fix vulnerabilities automatically