next@15.4.0-canary.39 vulnerabilities

The React Framework

  • latest version

    16.0.7

  • latest non vulnerable version

  • first published

    14 years ago

  • latest version published

    1 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
    • C
    Arbitrary Code Injection

    next is a react framework.

    Affected versions of this package are vulnerable to Arbitrary Code Injection via unsafe deserialization of RSC payloads from HTTP requests to Server Function endpoints. An unauthenticated attacker can execute arbitrary code on the server by sending malicious HTTP requests.

    Note:

    Serverless applications and applications that do not use a framework, bundler, or bundler plugin that supports React Server Components are not affected by this vulnerability.

    Next.js 13.x, Next.js 14.x stable, Pages Router applications, and the Edge Runtime are not affected.

    This vulnerability originates in the upstream React implementation. This advisory tracks the downstream impact on Next.js applications using the App Router.

    CVE-2025-66478 was originally announced for this vulnerability and later rejected as a duplicate of CVE-2025-55182.

    How to fix Arbitrary Code Injection?

    Upgrade next to version 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7 or higher.

    >=14.3.0-canary.77 <15.0.5>=15.1.0 <15.1.9>=15.2.0-canary.0 <15.2.6>=15.3.0-canary.0 <15.3.6>=15.4.0-canary.0 <15.4.8>=15.5.1-canary.0 <15.5.7>=16.0.0-beta.0 <16.0.7
    • 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