Arcadedb
Monthly
Privilege escalation in ArcadeDB before 26.7.3 allows any authenticated MCP user to fully bypass the database authorization framework. The MCP HTTP transport layer fails to bind the authenticated principal into the engine's permission context, causing all access control checks to silently resolve as no-ops regardless of the user's actual role. Affected users can perform arbitrary DDL, schema mutations, unrestricted database writes, and execute arbitrary JavaScript via the query tool - effectively gaining root-level database access from a low-privileged account. No public exploit has been identified at time of analysis and this CVE is not listed in CISA KEV, though the impact is severe for any deployment with MCP transport enabled.
Cleartext leakage of the HA cluster token in ArcadeDB's MCP get_server_settings tool allows any authenticated MCP user to escalate to full root-level server control in all versions before 26.7.3. The exposed arcadedb.ha.clusterToken can be replayed via the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers to impersonate the root user, turning a low-privilege information disclosure into a complete server compromise. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, the chained privilege escalation path significantly elevates real-world impact beyond the CWE-200 classification suggests.
Privilege escalation in ArcadeDB before 26.7.3 allows any user holding UPDATE_SCHEMA permission to create server-wide administrator accounts by crafting malicious JavaScript triggers. The root cause is that the real LocalDatabase object is bound into trigger execution contexts with GraalVM's HostAccess.ALL policy, exposing the full Java security API - including getSecurity().createUser() - without permission checks. No public exploit has been identified at time of analysis, but a vendor-released patch is available in 26.7.3 per the GitHub security advisory GHSA-38pf-6hp2-pxww.
OS command execution in ArcadeDB (arcadedb-engine) before 26.7.2 lets an authenticated user with UPDATE_SCHEMA permission escalate to full remote code execution on the host. Because ScriptTriggerExecutor whitelists java.lang.* for JavaScript trigger scripts, an attacker can create a trigger that calls Java.type("java.lang.Runtime").getRuntime().exec() (or ProcessBuilder) and runs arbitrary OS commands when the trigger fires. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis.
Permission bypass in ArcadeDB before 26.7.2 allows authenticated read-only users to execute privileged schema-mutation SQL operations that should require the UPDATE_SCHEMA permission. A user holding only a read-only API token can submit ALTER TYPE ... CUSTOM or ALTER TYPE ... BUCKETSELECTIONSTRATEGY statements to the HTTP command endpoint, invoking setCustomValue and setBucketSelectionStrategy on LocalDocumentType without any permission enforcement. The consequence is unauthorized corruption of schema metadata and bucket-selection strategy, potentially disrupting record routing and data integrity across the database. No public exploit has been identified at time of analysis and this CVE is not listed in CISA KEV; a vendor-released patch is available in version 26.7.2.
Scripting authorization bypass in ArcadeDB before 26.7.2 lets any authenticated database user - including read-only roles - run sandboxed JavaScript by submitting a SQL 'DEFINE FUNCTION ... LANGUAGE js' statement, defeating a control that was supposed to restrict scripting to security administrators. The prior GHSA-48qw-824m-86pr hardening added a UPDATE_SECURITY permission gate to the polyglot engine, but the SQL route to JavaScript never invokes it, so low-privilege users regain the very capability the gate was meant to remove. Reported by VulnCheck; the vendor advisory publicly documents a complete two-request exploitation recipe, and the vendor scores it CVSS 4.0 9.3 (Critical), though the runtime sandbox meaningfully limits real-world impact.
Cluster token exposure in ArcadeDB before 26.7.2 enables any authenticated user to escalate privileges to root-level administrative control. The GET /api/v1/server management endpoint returns the arcadedb.ha.clusterToken value in cleartext, which an attacker can replay via the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers to impersonate the root account. This two-stage privilege escalation grants full administrative capabilities including user creation, arbitrary database operations, and server shutdown - representing a near-total system compromise for any multi-tenant or shared ArcadeDB deployment. No public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog, but the exploitation path is mechanically trivial once credentials are obtained.
Cross-database authorization bypass (IDOR) in ArcadeDB before 26.7.2 lets attackers read and write any database on the server by supplying an arbitrary {database} parameter to the time series (/ts/*), batch, Prometheus, and Grafana HTTP handlers. Roughly 14 endpoints resolve the target database and call getDatabase(...) without invoking canAccessToDatabase(...), so a caller scoped to one database (or, per the code, potentially an anonymous request) gains full read/write over databases they were never granted. Reported by VulnCheck with a vendor patch (26.7.2) available; the GHSA advisory publishes concrete exploitation requests, and while EPSS is not provided the CVSS 4.0 base score is 9.3 (Critical). This is not in CISA KEV.
Privilege escalation in ArcadeDB before 26.7.3 allows any authenticated MCP user to fully bypass the database authorization framework. The MCP HTTP transport layer fails to bind the authenticated principal into the engine's permission context, causing all access control checks to silently resolve as no-ops regardless of the user's actual role. Affected users can perform arbitrary DDL, schema mutations, unrestricted database writes, and execute arbitrary JavaScript via the query tool - effectively gaining root-level database access from a low-privileged account. No public exploit has been identified at time of analysis and this CVE is not listed in CISA KEV, though the impact is severe for any deployment with MCP transport enabled.
Cleartext leakage of the HA cluster token in ArcadeDB's MCP get_server_settings tool allows any authenticated MCP user to escalate to full root-level server control in all versions before 26.7.3. The exposed arcadedb.ha.clusterToken can be replayed via the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers to impersonate the root user, turning a low-privilege information disclosure into a complete server compromise. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, the chained privilege escalation path significantly elevates real-world impact beyond the CWE-200 classification suggests.
Privilege escalation in ArcadeDB before 26.7.3 allows any user holding UPDATE_SCHEMA permission to create server-wide administrator accounts by crafting malicious JavaScript triggers. The root cause is that the real LocalDatabase object is bound into trigger execution contexts with GraalVM's HostAccess.ALL policy, exposing the full Java security API - including getSecurity().createUser() - without permission checks. No public exploit has been identified at time of analysis, but a vendor-released patch is available in 26.7.3 per the GitHub security advisory GHSA-38pf-6hp2-pxww.
OS command execution in ArcadeDB (arcadedb-engine) before 26.7.2 lets an authenticated user with UPDATE_SCHEMA permission escalate to full remote code execution on the host. Because ScriptTriggerExecutor whitelists java.lang.* for JavaScript trigger scripts, an attacker can create a trigger that calls Java.type("java.lang.Runtime").getRuntime().exec() (or ProcessBuilder) and runs arbitrary OS commands when the trigger fires. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis.
Permission bypass in ArcadeDB before 26.7.2 allows authenticated read-only users to execute privileged schema-mutation SQL operations that should require the UPDATE_SCHEMA permission. A user holding only a read-only API token can submit ALTER TYPE ... CUSTOM or ALTER TYPE ... BUCKETSELECTIONSTRATEGY statements to the HTTP command endpoint, invoking setCustomValue and setBucketSelectionStrategy on LocalDocumentType without any permission enforcement. The consequence is unauthorized corruption of schema metadata and bucket-selection strategy, potentially disrupting record routing and data integrity across the database. No public exploit has been identified at time of analysis and this CVE is not listed in CISA KEV; a vendor-released patch is available in version 26.7.2.
Scripting authorization bypass in ArcadeDB before 26.7.2 lets any authenticated database user - including read-only roles - run sandboxed JavaScript by submitting a SQL 'DEFINE FUNCTION ... LANGUAGE js' statement, defeating a control that was supposed to restrict scripting to security administrators. The prior GHSA-48qw-824m-86pr hardening added a UPDATE_SECURITY permission gate to the polyglot engine, but the SQL route to JavaScript never invokes it, so low-privilege users regain the very capability the gate was meant to remove. Reported by VulnCheck; the vendor advisory publicly documents a complete two-request exploitation recipe, and the vendor scores it CVSS 4.0 9.3 (Critical), though the runtime sandbox meaningfully limits real-world impact.
Cluster token exposure in ArcadeDB before 26.7.2 enables any authenticated user to escalate privileges to root-level administrative control. The GET /api/v1/server management endpoint returns the arcadedb.ha.clusterToken value in cleartext, which an attacker can replay via the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers to impersonate the root account. This two-stage privilege escalation grants full administrative capabilities including user creation, arbitrary database operations, and server shutdown - representing a near-total system compromise for any multi-tenant or shared ArcadeDB deployment. No public exploit has been identified at time of analysis and this CVE is not listed in the CISA KEV catalog, but the exploitation path is mechanically trivial once credentials are obtained.
Cross-database authorization bypass (IDOR) in ArcadeDB before 26.7.2 lets attackers read and write any database on the server by supplying an arbitrary {database} parameter to the time series (/ts/*), batch, Prometheus, and Grafana HTTP handlers. Roughly 14 endpoints resolve the target database and call getDatabase(...) without invoking canAccessToDatabase(...), so a caller scoped to one database (or, per the code, potentially an anonymous request) gains full read/write over databases they were never granted. Reported by VulnCheck with a vendor patch (26.7.2) available; the GHSA advisory publishes concrete exploitation requests, and while EPSS is not provided the CVSS 4.0 base score is 9.3 (Critical). This is not in CISA KEV.