Which versions of ArcadeDB are affected by EUVD-2026-51987?

ArcadeDB versions prior to 26.7.3 contain a privilege escalation vulnerability that allows authenticated cluster users to gain full administrative control over database servers.. A patch is available.

How to fix or mitigate EUVD-2026-51987?

Within 24 hours: identify all ArcadeDB instances and document current versions in your environment. Within 7 days: test ArcadeDB 26.7.3 in a staging environment to verify compatibility with your cluster configuration. Within 30 days: apply the patch to all production ArcadeDB clusters, verify that cluster tokens are no longer exposed in MCP tool responses, and rotate all HA cluster tokens as a precautionary measure.

ArcadeDB EUVD-2026-51987

Q: What is the CVSS score of EUVD-2026-51987?

EUVD-2026-51987 has a CVSS 4.0 base score of 7.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

| CVE-2026-67357 HIGH

Information Exposure (CWE-200)

2026-08-02 VulnCheck

GHSA-7qj8-rw8h-hhxv

Information Disclosure Arcadedb Arcadedata

7.7

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

7.7 HIGH

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.5 HIGH

Network-reachable MCP tool requires low-privilege authentication (PR:L); AC:H because HA cluster token must be configured; full C/I/A from root impersonation; no scope change as impact stays within the ArcadeDB server.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 02, 2026 - 13:03 vuln.today

Patch available

Aug 02, 2026 - 13:01 EUVD

CVE Published

Aug 02, 2026 - 12:15 cve.org

HIGH 7.7

DescriptionCVE.org

ArcadeDB versions before 26.7.3 contain an information disclosure vulnerability in the MCP get_server_settings tool that leaks the arcadedb.ha.clusterToken in cleartext. Attackers with MCP access can retrieve the cluster token and use it with X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User headers to impersonate root and achieve full server compromise.

AnalysisAI

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.

Technical ContextAI

ArcadeDB (CPE: cpe:2.3:a:arcadedata:arcadedb:*) is a multi-model NoSQL database supporting graph, document, key-value, and time-series data. The MCP (Model Context Protocol) interface exposes a get_server_settings tool that returns server configuration metadata - including the arcadedb.ha.clusterToken, the shared secret used for High Availability cluster node authentication. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) describes the root cause: this internal cluster credential is returned in cleartext to any caller with MCP access, regardless of privilege level. The exploitable design flaw is that ArcadeDB honors the X-ArcadeDB-Cluster-Token and X-ArcadeDB-Forwarded-User HTTP headers for identity assertion, meaning possession of the cluster token is sufficient to forge requests as any user, including root. This conflates an internal inter-node authentication mechanism with a per-user authorization boundary, enabling a horizontal-to-vertical privilege escalation chain.

RemediationAI

Upgrade to ArcadeDB 26.7.3 or later, which resolves the cleartext token exposure in the MCP get_server_settings tool per the vendor advisory at https://github.com/ArcadeData/arcadedb/security/advisories/GHSA-p9wc-4fhr-78wm. For deployments that cannot immediately upgrade, restrict MCP interface access to only explicitly trusted administrative users - since PR:L is a prerequisite, reducing the pool of MCP-capable accounts directly reduces exposure. Additionally, rotate the arcadedb.ha.clusterToken on all affected instances to invalidate any tokens that may already have been exfiltrated; this is a critical compensating step even post-upgrade. If HA clustering is not required, disabling the feature removes the token from the configuration entirely and eliminates the privilege-escalation path while still leaving the information disclosure issue present. Network-level controls (firewall rules, VPN requirements) that restrict who can reach the MCP interface reduce the attack surface but do not remediate the underlying flaw.