16.2.6
14 years ago
7 days ago
Known vulnerabilities in the next package. This does not include vulnerabilities belonging to this package’s dependencies.
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 |
|---|---|
next is a react framework. Affected versions of this package are vulnerable to Authentication Bypass Using an Alternate Path or Channel via the Note: This vulnerability relates to the incomplete fix of CVE-2026-44575 How to fix Authentication Bypass Using an Alternate Path or Channel? Upgrade | >=15.2.0-canary.0 <15.5.18>=16.0.0-beta.0 <16.2.6 |
next is a react framework. Affected versions of this package are vulnerable to Authentication Bypass Using an Alternate Path or Channel in the handling of segment-prefetch routes. An attacker can gain unauthorized access to protected content by crafting Notes:
How to fix Authentication Bypass Using an Alternate Path or Channel? Upgrade | >=15.2.0-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the CSP nonce headers. An attacker can inject malicious scripts into cached HTML responses by supplying malformed nonce values, which may then be executed in the browsers of subsequent visitors. This is possible when applications are deployed behind shared caches and rely on request-derived nonce values. How to fix Cross-site Scripting (XSS)? Upgrade | >=13.4.13-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Incorrect Authorization in the How to fix Incorrect Authorization? Upgrade | >=12.2.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via crafted WebSocket upgrade requests. An attacker can access internal or external resources by sending specially crafted requests with absolute-url that cause the server to proxy connections to arbitrary destinations, potentially exposing sensitive internal services or cloud metadata endpoints. How to fix Server-side Request Forgery (SSRF)? Upgrade | >=13.4.13-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the How to fix Cross-site Scripting (XSS)? Upgrade | >=13.0.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the Image Optimization API when handling requests to the Note: This is only exploitable if the default image loader is used and the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=10.0.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Authentication Bypass Using an Alternate Path or Channel via dynamic full-route RSC requests in the deployment adapter. An attacker can gain unauthorized access to protected content by injecting a URL with query params that got misclassified by the How to fix Authentication Bypass Using an Alternate Path or Channel? Upgrade | >=15.4.0-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling involving Partial Prerendering in the Cache Components feature. An attacker can exhaust the connection pool by sending malicious POST requests that cause a deadlock. This, in turn, causes connections to be left open and consumes file descriptors and server capacity. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=15.0.0-rc.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Use of Weak Hash via collisions in the How to fix Use of Weak Hash? Upgrade | >=13.4.6-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Interpretation Conflict via improper handling of shared cache entries for React Server Component responses. An attacker can cause unintended component payloads to be served to other users by manipulating shared cache behavior through crafted requests. How to fix Interpretation Conflict? Upgrade | >=14.2.0-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Acceptance of Extraneous Untrusted Data With Trusted Data through the improper handling of the How to fix Acceptance of Extraneous Untrusted Data With Trusted Data? Upgrade | >=12.2.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via server function endpoints. An attacker can cause out-of-memory exceptions or induce excessive CPU usage by sending malicious Note: Only React apps that use React Server Components are vulnerable. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=13.0.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |