Executive brief
ArcadeDB is a graph and document database server that manages configuration secrets including cluster authentication tokens. The MCP (Model Context Protocol) interface exposes these tokens in plaintext through the get_server_settings tool, allowing non-root users with MCP access to retrieve the cluster authentication token and impersonate root administrators, leading to complete server compromise.
Technical details
The vulnerability is an information disclosure (CWE-200) in ArcadeDB's MCP get_server_settings tool, which fails to redact the arcadedb.ha.clusterToken configuration value. The root cause is that GetServerSettingsTool.maskSensitive() only redacts keys containing "password" in their name, but arcadedb.ha.clusterToken lacks "password" in its key name despite being marked as hidden by GlobalConfiguration.isHidden(). An attacker with MCP access and non-root privileges can call the get_server_settings tool to retrieve the cluster token in cleartext. The token serves as the trust anchor for validateClusterForwardedAuth, which runs before standard authorization checks on the main HTTP port and unconditionally trusts requests bearing X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User: root headers, enabling full root impersonation. The vulnerability requires MCP to be enabled and the cluster token to be explicitly configured (non-default). Patch available in version 26.7.3.
Affected products
- ArcadeData ArcadeDB before 26.7.3
Timeline
- 2026-07-17: disclosed: GitHub Security Advisory GHSA-p9wc-4fhr-78wm published
- 2026-08-02: advisory: CVE-2026-67357 published on NVD
- 2026-07-17: patched: Patched in version 26.7.3