ArcadeDB GraalVM Sandbox Bypass Enables Arbitrary File Read

ArcadeDB versions prior to 26.8.1 suffer from a critical sandbox escape vulnerability in their GraalVM JavaScript execution environment. The flaw stems from improper validation of package names using unescaped regular expressions in the allowlist enforcement mechanism, creating a gap that skilled attackers can exploit. Users with trigger creation privileges can leverage Java.type() to instantiate restricted classes like java.util.zip.ZipFile and java.util.jar.JarFile, gaining the ability to read arbitrary files from the host system with the privileges of the ArcadeDB server process. This vulnerability affects database administrators, application developers using ArcadeDB for data processing, and organizations running ArcadeDB in production environments where trigger functionality is enabled.

While this CVE currently maps to zero MITRE ATT&CK techniques in standard frameworks, Casky's Claude-powered analysis would correlate this attack pattern with Privilege Escalation (T1548) and Defense Evasion (T1562) techniques, as attackers bypass sandbox restrictions to gain unauthorized system access. Practitioners using Casky would observe findings flagged around suspicious Java reflection patterns, unexpected filesystem access attempts from database processes, and trigger definitions containing Java.type() calls accessing java.io or java.util.zip classes. The extended reasoning capability would identify the logical chain: trigger creation → GraalVM sandbox → regex bypass → unrestricted class instantiation → file system access, enabling security teams to detect this exploitation pattern before sensitive data exfiltration occurs.