next@15.5.16

The React Framework

  • latest version

    16.2.9

  • latest non vulnerable version

  • first published

    14 years ago

  • latest version published

    11 days ago

  • licenses detected

  • 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
    VulnerabilityVulnerable Version
    • H
    Authentication Bypass Using an Alternate Path or Channel

    next is a react framework.

    Affected versions of this package are vulnerable to Authentication Bypass Using an Alternate Path or Channel via the middleware.ts with Turbopack enabled. An attacker can gain unauthorized access to protected resources by bypassing authentication mechanisms through specially crafted segment-prefetch routes.

    Note: This vulnerability relates to the incomplete fix of CVE-2026-44575

    How to fix Authentication Bypass Using an Alternate Path or Channel?

    Upgrade next to version 15.5.18, 16.2.6 or higher.

    >=15.2.0-canary.0 <15.5.18>=16.0.0-beta.0 <16.2.6
    • 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 due to the lack of an upper bound on the disk cache used by the image optimization. An attacker can exhaust disk storage by generating a large number of unique image optimization variants, leading to service disruption.

    How to fix Allocation of Resources Without Limits or Throttling?

    Upgrade next to version 16.1.7, 16.2.0-canary.54 or higher.

    >=10.0.0 <16.1.7>=16.2.0-canary.0 <16.2.0-canary.54
    • H
    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 via the Partial Prerendering resume endpoint when unauthenticated POST requests with the Next-Resume: 1 header are processed and attacker-controlled postponed state data is handled. An attacker can cause the server process to crash and exhaust system memory by sending large or highly compressed payloads that are buffered or decompressed without size limits.

    Note:

    This is only exploitable if the application is running with experimental.ppr: true or cacheComponents: true configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable.

    How to fix Allocation of Resources Without Limits or Throttling?

    Upgrade next to version 15.6.0-canary.61, 16.1.1-canary.16, 16.1.5 or higher.

    >=15.0.0-canary.0 <15.6.0-canary.61>=16.0.0-beta.0 <16.1.1-canary.16>=16.1.1 <16.1.5