EUVD-2026-54789
GHSA-4p6x-rj5h-hg93
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local-only attack requiring low-privilege MCP tool invocation; limited confidentiality, integrity, and availability impact with no scope change to other systems.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Path traversal in astralisone's rive-mcp-server-core MCP server allows local low-privileged users to escape the intended directory boundary by supplying crafted sequences in the libraryId argument of the importRiveFile flow, enabling unauthorized read and partial write access to files on the host system. All commits up to db1d0cc4cd52589116360428b7504fd0ca748b3e of the rolling-release project are affected, with no vendor patch issued and no vendor response to disclosure at time of analysis. A proof-of-concept exploit exists (CVSS 4.0 E:P), though no confirmed active exploitation (CISA KEV) has been reported.
Technical ContextAI
The vulnerability exists in packages/mcp-server/src/tools/importRiveFile.ts, a TypeScript module within an MCP (Model Context Protocol) server designed to import Rive animation library assets. MCP servers act as local tool-serving processes consumed by AI agent frameworks, making them a local-privilege attack surface. The libraryId parameter is used in constructing a file path without sufficient sanitization or canonicalization - a textbook CWE-22 (Path Traversal) root cause. An attacker can inject sequences such as ../../ into libraryId to resolve paths outside the intended base directory. CPE cpe:2.3:a:astralisone:rive-mcp-server-core:*:*:*:*:*:*:*:* covers all versions, consistent with the rolling-release model where no discrete version pinning is available.
RemediationAI
No vendor-released patch has been identified at time of analysis; the vendor had not responded to the responsible disclosure at the time of reporting. As an immediate code-level mitigation for self-hosters, wrap the libraryId input in a path canonicalization check - resolve the absolute path and verify it falls within the expected base directory before any file operation, rejecting inputs that escape the boundary. As an operational control, restrict local system access to the MCP server process to only fully trusted users and processes, reducing the pool of potential attackers; note this does not eliminate the vulnerability but raises the bar. Monitor file-access logs for traversal sequences (e.g., ../) in MCP tool invocations to detect exploitation attempts. Track the GitHub issue at https://github.com/astralisone/rive-mcp-server-core/issues/2 and VulDB advisory https://vuldb.com/vuln/387027 for patch availability, and upgrade to a fixed commit as soon as one is published.
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today