Vulnerabilities

16 via 16 paths

Dependencies

23

Source

GitHub

Find, fix and prevent vulnerabilities in your code.

Severity
  • 3
  • 5
  • 7
  • 1
Status
  • 16
  • 0
  • 0

critical severity
new

Dependency on Vulnerable Third-Party Component

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.4.1.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Dependency on Vulnerable Third-Party Component via the sharp image processing dependency used by next/image. A vulnerable version of sharp is bundled as an optional dependency, and an attacker can exploit a flaw in that library to achieve remote code execution, full confidentiality loss, integrity loss, and availability loss on both the application and system level.

Remediation

Upgrade next to version 15.5.28, 16.4.1 or higher.

References

critical severity
new

Deserialization of Untrusted Data

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.4.1.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Deserialization of Untrusted Data via a flaw in the React Server Component transport protocol implementation, specifically in the serializeReadableStream, serializeReader, and serializeAsyncIterable functions within the compiled react-server-dom-turbopack and react-server-dom-webpack client bundles. The stream part identifiers used when appending chunks to FormData are constructed without a distinguishing prefix ("S"), allowing stream data to be written to incorrect form field keys. An attacker who can influence the server component data stream can exploit this to corrupt the transport payload, potentially achieving arbitrary code execution on the client or server.

Details

Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.

Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.

Remediation

Upgrade next to version 16.4.1 or higher.

References

critical severity
new

Remote Code Execution (RCE)

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.4.1.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Remote Code Execution (RCE) in applications using App router with Cache Component.

Remediation

Upgrade next to version 16.4.1 or higher.

References

high severity

Use After Free

  • Vulnerable module: sharp
  • Introduced through: sharp@0.35.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › sharp@0.35.4
    Remediation: Upgrade to sharp@0.35.5.

Overview

sharp is a High performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, GIF, AVIF and TIFF images

Affected versions of this package are vulnerable to Use After Free in entity_insert() and the entity map held on XmlState, which is shared between the outer parse and a recursive XInclude, so inserting an entity whose name already exists replaces the first entry and its Drop implementation calls xmlFreeNode() while the outer xmlCtxtParseEntity() is still using that 144 byte xmlEntity. An attacker can corrupt process memory by supplying an SVG document whose xi:include pulls in another document redefining an entity that is already active. This requires the application to parse attacker supplied SVG with XInclude processing reached, and the entity names must collide across the outer document and the included one.

Remediation

Upgrade sharp to version 0.35.5 or higher.

References

high severity
new

Use After Free

  • Vulnerable module: sharp
  • Introduced through: sharp@0.35.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › sharp@0.35.4
    Remediation: Upgrade to sharp@0.35.5.

Overview

sharp is a High performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, GIF, AVIF and TIFF images

Affected versions of this package are vulnerable to Use After Free via a memory-related vulnerability in the bundled librsvg dependency. An attacker can supply an SVG image that, when decoded through librsvg, triggers the memory corruption and results in arbitrary code execution on glibc-based Linux systems.

Note: This is only exploitable when the node executable is not compiled as a Position Independent Executable (PIE); the official Node.js binaries do not use this hardening feature, making them susceptible.

Remediation

Upgrade sharp to version 0.35.5 or higher.

References

high severity

Server-side Request Forgery (SSRF)

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the Image Optimization remote fetch, which resolves and requests an allowlisted remote URL without constraining the address that name resolves to, so a host permitted by images.remotePatterns can direct the fetch at an internal address. An attacker can make the server issue requests to private network addresses and read the responses back through the image endpoint, by controlling the DNS records of a host that matches an allowlist entry so the name resolves to that internal address at fetch time. This requires images.remotePatterns to be configured with at least one host whose DNS entries the attacker controls or can influence, so applications with no images.remotePatterns configured are unaffected.

Workaround

This vulnerability can be avoided by removing from images.remotePatterns any host whose DNS entries are not trusted.

Remediation

Upgrade next to version 16.3.8 or higher.

References

high severity
new

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.4.1.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via App Router's Server Actions handler, where requests cause excessive CPU usage that blocks processing of further requests in the same process. An unauthenticated remote attacker can send requests to exhaust CPU resources, rendering the application unable to serve subsequent requests.

Remediation

Upgrade next to version 15.5.28, 16.4.1 or higher.

References

high severity
new

Excessive Iteration

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.4.1.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Excessive Iteration via a crafted request using App Router with at least one Server Action which can lead to excessive CPU usage blocking processing of further requests in the same process.

Remediation

Upgrade next to version 15.5.28, 16.4.1 or higher.

References

medium severity

Origin Validation Error

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Origin Validation Error via the MCP middleware endpoint /_next/mcp, where insufficient host validation allows a DNS rebinding attack. An attacker who controls a malicious DNS server can cause a victim's browser to treat the attacker's domain as a same-origin resource, bypassing the cross-site request protections applied in development mode and gaining read access to confidential data exposed by the MCP server.

Remediation

Upgrade next to version 16.3.8 or higher.

References

medium severity

Use of Cache Containing Sensitive Information

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via incorrect cache keying in nested 'use cache' function handlers that access root params. When Cache Components is enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function which reads a root param can be keyed incorrectly when the inner call is served from an existing cache entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value, whether the page is prerendered at build time, at runtime, or rendered dynamically, and shared cache headers allow downstream caches to redistribute the mismatched content further.

Note: This is only exploitable when the cacheComponents: true option is enabled and the application uses nested 'use cache' functions where the inner function reads a root param.

Remediation

Upgrade next to version 16.3.8 or higher.

References

medium severity

Use of Cache Containing Sensitive Information

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via insufficient scoping of response cache keys to their source route in base-server.ts and related export/build pipeline files. When multiple routes share a cache key, a response generated for one route can be served to requests for a different route, allowing an attacker to cause incorrect cached content to be returned to users, resulting in limited availability impact through cache poisoning or stale-data delivery.

Remediation

Upgrade next to version 16.3.8, 15.5.27 or higher.

References

medium severity

Use of Cache Containing Sensitive Information

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via cross-request deduplication in the use-cache-wrapper.ts cache function, where draft mode state is not accounted for when sharing cached fills across concurrent requests. A draft mode request can join a pending public cache fill and receive published content instead of draft content, or conversely, a fill executed under draft mode containing unpublished content can be registered and served to non-draft requests.

Note: This is only exploitable when the 'use cache' directive is in use and concurrent requests occur, one of which has draft mode enabled.

Remediation

Upgrade next to version 16.3.8 or higher.

References

medium severity

Use of Cache Containing Sensitive Information

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via insufficient scoping of response cache keys in the server's cache key generation logic, where cache keys are not bound to their source route. An attacker can trigger a cache key collision between distinct routes, causing one route's cached response to be served for a different route and resulting in partial availability loss for affected endpoints.

Remediation

Upgrade next to version 15.5.27, 16.3.8, 16.3.8 or higher.

References

medium severity

Use of Cache Containing Sensitive Information

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via insufficient scoping of response cache keys in the server's route caching logic in base-server.ts. Because cache keys are not bound to their source route, a response cached for one route can be served for a different route that shares the same key, allowing an attacker to poison the cache and cause other users to receive incorrect or attacker-influenced responses, or to trigger a denial of service through cache corruption.

Remediation

Upgrade next to version 15.5.27, 16.3.8 or higher.

References

medium severity

Use of Cache Containing Sensitive Information

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via cross-request deduplication in the 'use cache' mechanism, where draft mode state is not accounted for when sharing cached fills between concurrent requests. A cache fill executed under draft mode - which may contain unpublished content - can be registered and served to other non-draft requests, and conversely a draft mode request can join a pending public fill and receive published content instead of draft content, leaking unpublished data across request boundaries.

Remediation

Upgrade next to version 16.3.8 or higher.

References

low severity

Origin Validation Error

  • Vulnerable module: next
  • Introduced through: next@16.3.4

Detailed paths

  • Introduced through: @arthelokyo/tailnext@onwidget/tailnext › next@16.3.4
    Remediation: Upgrade to next@16.3.8.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Origin Validation Error via the MCP middleware (get-mcp-middleware.ts) and the cross-site dev request blocker (block-cross-site-dev.ts), which fail to adequately validate the request origin against the host. An attacker who controls a DNS record can rebind a malicious domain to the victim's localhost address, causing the victim's browser to issue cross-origin requests to the local Next.js development server that bypass the intended origin checks, resulting in limited confidentiality and integrity impact.

Remediation

Upgrade next to version 16.3.8 or higher.

References