Description

A vulnerability has been found in astralisone rive-mcp-server-core up to db1d0cc4cd52589116360428b7504fd0ca748b3e. This affects an unknown part of the file packages/mcp-server/src/tools/importRiveFile.ts of the component importRiveFile Flow. Such manipulation of the argument libraryId leads to path traversal. The attack needs to be performed locally. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.3",
  "pubDate": "2026-08-08T14:16:24.063Z",
  "pubdate": "2026-08-08T14:16:24.063Z",
  "executiveSummary": "A path traversal vulnerability has been identified in the astralisone rive-mcp-server-core component, specifically within the importRiveFile Flow processing logic. The flaw exists in the handling of the libraryId argument within the packages/mcp-server/src/tools/importRiveFile.ts file, affecting versions up to commit db1d0cc4cd52589116360428b7504fd0ca748b3e.\nThe vulnerability allows a local attacker to manipulate the libraryId parameter, facilitating unauthorized traversal of the underlying filesystem. Due to the rolling release nature of the product, static version identifiers are unavailable, heightening the risk for deployments utilizing affected source trees.\nSuccessful exploitation of this flaw can compromise the integrity and confidentiality of the host filesystem by exposing arbitrary files accessible to the application execution context. The attack vector strictly requires local execution capabilities on the target system.",
  "technicalDetails": "The vulnerability stems from insufficient sanitization, validation, and canonicalization of user-supplied input passed to the libraryId parameter within the importRiveFile Flow. The vulnerable logic resides in the packages/mcp-server/src/tools/importRiveFile.ts file of the astralisone rive-mcp-server-core project.\nWhen an attacker supplies a specially crafted string containing directory traversal sequences (such as dot-dot-slash patterns) via the libraryId argument, the application fails to restrict file system operations to the intended base directory. Consequently, the underlying file handling routines resolve the manipulated path relative to the root or working directory, allowing traversal outside the designated repository or workspace boundaries.\nThe exploitation vector requires local access to the system where the mcp-server-core component is deployed and executed. An attacker leverages this local access to invoke the vulnerable tool flow with malicious input arguments designed to traverse the directory structure. Depending on the runtime privileges of the process executing the server, this permits the unauthorized reading or processing of sensitive files outside the intended scope of the importRiveFile functionality.\nThe affected scope includes all revisions of astralisone rive-mcp-server-core up to commit hash db1d0cc4cd52589116360428b7504fd0ca748b3e. Because the product utilizes a continuous delivery rolling release model, explicit version numbers are absent, necessitating dependency checks against the exact commit identifier."
}