Arbitrary file write via unchecked libraryId path
Published Aug 8, 2026 · Updated Aug 8, 2026
Path traversal in Astralis One Rive MCP Server - Core System allows local users to write files outside its manifest directory. The importRiveFile flow assigns a caller-controlled libraryId to library.id, then saveLibrary joins it into a filename without checking that the resolved path remains under manifestsPath. Invocation access to the MCP tool is required, and writes are limited to .library.json-suffixed paths permitted by the server process account.
Summary
What happened
Path traversal in Astralis One Rive MCP Server - Core System allows local users to write files outside its manifest directory. The importRiveFile flow assigns a caller-controlled libraryId to library.id, then saveLibrary joins it into a filename without checking that the resolved path remains under manifestsPath. Invocation access to the MCP tool is required, and writes are limited to .library.json-suffixed paths permitted by the server process account.
The record
- CVE
- CVE-2026-19288
- Published
- Aug 8, 2026
- Updated
- Aug 8, 2026
- Vendor
- Astralis One
- Product
- Rive MCP Server - Core System
- Classifications
- CWE-22
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 8, 2026CVE publishedPublication date reported by the CVE source.
- Aug 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=db1d0cc4cd52589116360428b7504fd0ca748b3e
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- libraryId traversal JSON-RPC proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo