Summary
ArcadeDB: Privilege escalation via reader role in /api/v1/command JS scripting language, arbitrary host file read
Workarounds
Until upgraded, do not grant command/query access on the HTTP API to untrusted users, and treat any account that can reach /api/v1/command as capable of code execution. Note that after the fix, non-administrator accounts can no longer run js/polyglot scripts over HTTP.
Credit
Reported by @kyojune76.
Impact
A user holding only reader (read-only) privileges on a single database could execute arbitrary JVM code by sending a "language": "js" command to the POST /api/v1/command/{database} HTTP endpoint, and use it to read arbitrary files on the host filesystem (e.g. /etc/passwd, configuration files), outside the scope of the database itself.
Two cooperating defects made this possible:
- Missing authorization on the scripting path (CWE-863 / CWE-269). Polyglot script execution (
jsand other GraalVM languages) never went through the database authorization checks applied to SQL/Cypher, so any authenticated principal - regardless of database role - could run scripts. - Sandbox whitelist bypass. The GraalVM sandbox restricts direct class lookups to a configured
allowedPackageslist, but a script could reach arbitrary classes by reflecting off the bounddatabaseobject:database.getClass().getClassLoader().loadClass("java.io.File").
Process creation was already blocked (allowCreateProcess(false)), so the confirmed impact is host file read, not OS command execution. Confidentiality: High. Integrity/Availability: None.
This is a distinct entry point and root cause from CVE-2026-44221, CVE-2026-54076 and CVE-2026-54077, and is reproducible on builds that already contain those fixes.
The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.
GHSA-48QW-824M-86PR has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (26.7.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The fix is applied in the engine so it covers every entry point (HTTP command, HA-forwarded commands, MCP analyze), not only the HTTP handler:
- Polyglot script execution now requires the
updateSecuritydatabase-administrator permission oncommand,analyzeandregisterFunctions. The check runs on the request thread that carries the authenticated user and is a no-op in embedded mode and internal/system contexts (schema load, HA replication apply). - The GraalVM host-access policy now denies access to
java.lang.Class,java.lang.ClassLoaderandjava.lang.reflectmembers, closing the reflection escape that bypassedallowedPackages- even for authorized administrators - while leaving normal method calls on bound objects and explicitJava.type(...)lookups (governed byallowedPackages) working.
Frequently Asked Questions
- What is GHSA-48QW-824M-86PR? GHSA-48QW-824M-86PR is a high-severity improper privilege management vulnerability in com.arcadedb:arcadedb-server (maven), affecting versions < 26.7.1. It is fixed in 26.7.1. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
- How severe is GHSA-48QW-824M-86PR? GHSA-48QW-824M-86PR has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of com.arcadedb:arcadedb-server are affected by GHSA-48QW-824M-86PR? com.arcadedb:arcadedb-server (maven) versions < 26.7.1 is affected.
- Is there a fix for GHSA-48QW-824M-86PR? Yes. GHSA-48QW-824M-86PR is fixed in 26.7.1. Upgrade to this version or later.
- Is GHSA-48QW-824M-86PR exploitable, and should I be worried? Whether GHSA-48QW-824M-86PR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-48QW-824M-86PR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-48QW-824M-86PR? Upgrade
com.arcadedb:arcadedb-serverto 26.7.1 or later.